Software Development Skills

Use when the user says "weekly PR health" / "cycle time" / "reviewer load" / "DORA-lite" / "PR velocity" — pulls the last 7 days of PRs from a Composio-connected code host and computes five metrics (PRs merged, median cycle time, largest PR size, reviewer concentration, open-to-merge age) with a one-line diagnosis per anomaly, written to pr-velocity/{YYYY-Www}.md.

Use when the user says "audit our dev setup" / "setup time, build time, paper cuts" / "DX audit" — reads README + CONTRIBUTING + Makefile + package.json scripts + docker-compose + .env.example + CI config via the connected code host, estimates setup time from discrete steps, checks CI history for build time, and surfaces the top 5 paper cuts (missing env vars, flaky scripts, bad error messages, outdated commands) with suggested fixes. Draft only; never pushes fixes.

Use when the user says "audit my observability" / "audit logging/tracing/alerting" / "what are we blind to" / "review my Sentry/Datadog setup" — reads the connected observability stack + engineering-context architecture and produces a 3-column matrix (signal × coverage × gap) across errors / traces / logs / alerts / SLOs, plus a top-5 fix list ranked by blast-radius reduction.

Use when the user says "draft API docs for {endpoint}" / "human docs for our OpenAPI spec" / "document this endpoint" — reads an OpenAPI spec (openapi.yaml / swagger.json) from the connected code host, or accepts a pasted representative request/response, and writes Stripe-grade human API docs per endpoint with purpose, params table, request body, response body, error codes, curl example, and SDK snippet. Draft only; never invents API behavior.

Use when the user says "draft a design doc for {feature}" / "write an RFC for {feature}" / "design this before I build it" — produces a full design doc with Context, Goals, Non-goals, Proposed design, Alternatives considered, Risks, and Open questions, grounded in the engineering context doc, written to design-docs/{feature-slug}.md.

Use when the user says "draft a runbook for {system}" / "write me an ops doc for {failure mode}" / "document how to {operational task}" — produces a command-first ops doc with bash snippets + placeholders, dashboard URLs, rollback commands, and if-this-fails decision branches. No prose walls — every section is a command block or a decision branch.

Use when the user says "is {release} ready to deploy" / "run the deploy gate checklist" / "GO or NO-GO on {release}" — pre-deploy gate checklist (tests green, migrations backwards-compat, feature flags, rollback plan, on-call aware, runbook updated) with green/yellow/red per gate and a final GO / NO-GO / SOFT-GO verdict. Never runs deploy — agent produces the verdict; user clicks the button.

Use when the user says "draft my standup" / "what's my standup today" / "Monday standup" — pulls recent commits and PR activity from the connected code host, pulls recently closed tickets from the connected issue tracker, mixes in user notes, and produces a three-bullet Yesterday / Today / Blockers artifact. I never post on the user's behalf.

Use when the user says "weekly technical pulse" / "what did {competitor} ship this week" / "technical teardown of {competitor}" — fetches engineering-focused competitor signals via Composio (engineering blog posts, GitHub org activity, public changelog, API diffs) and writes either a single-competitor teardown or an N-competitor weekly digest.

Use when the user says "write the onboarding guide" / "new-engineer onboarding" / "day-1 doc" — reads the engineering context doc and the repo structure (README, CONTRIBUTING, Makefile, package.json scripts, docker-compose, .env.example) via the connected code host, and writes a single running onboarding-guide.md at the agent root with First day / First week / First month, repo map, verified setup steps, conventions, ownership (if team > 1), FAQ. Draft only; never auto-commits.

Use when the user says "write a how-to for {feature}" / "tutorial for {integration}" / "walk a user through {flow}" — produces a Diátaxis-aligned tutorial (learning-oriented, concrete end-to-end flow the reader can run) with overview, prerequisites, numbered steps with working code blocks, troubleshooting, next steps. Draft only; never publishes to a docs site.