メニュー
Fix a bug following project standards. Use when fixing defects, debugging issues, or resolving reported problems. Triggers on "fix bug", "debug", "fix issue", "resolve bug".
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | bug-fix |
| description | Fix a bug following project standards. Use when fixing defects, debugging issues, or resolving reported problems. Triggers on "fix bug", "debug", "fix issue", "resolve bug". |
| allowed-tools | Read, Edit, Write, Bash, Grep, Glob, Task |
Full workflow: CONTRIBUTION_GUIDE.md
When a test, build, or lint fails mid-flow — before making any more changes:
Rationale: failures compound. A bug unresolved at step N makes every change N+1…N+k incorrect. We observed this in #1871 (consensus_vote silent hang) — the symptoms looked like adapter timeouts, the cause was missing overall-deadline race.
Run this order before "Implement fix." Skipping steps produces symptom-level patches that regress.
pnpm lint && pnpm typecheck && pnpm test plus any integration/smoke test for the affected area.Debugging tempts four recurring shortcuts. Each is a trap.
| Excuse | Counter |
|---|---|
| "I know what the bug is" | Unverified guesses resolve only ~70% of the time. Reproduce first — the cost of confirming is minutes; the cost of a wrong fix is hours plus a regression. |
| "The failing test must be wrong" | Sometimes true, but verify against the spec before changing the test. A test asserting correct-but-inconvenient behavior gets "fixed" to assert the bug. |
| "It works on my machine" | Environment is a variable. Diff Node version, env vars, lockfile drift, CI container, clock/timezone, file system case sensitivity. |
| "This is flaky, ignore it" | Flaky = the test is exposing a real race/ordering/timing bug. Fix the intermittency or understand why it happens. .skip with a TODO is a ticking debt. |
Create/verify GitHub issue with reproduction steps
gh issue list --state open
gh issue create --title "bug: [description]" --label "bug"
Write failing test that demonstrates the bug
pnpm test -- --watch
Implement fix — minimal changes, don't refactor surrounding code
Verify test passes
pnpm lint && pnpm typecheck && pnpm test
Check for similar bugs elsewhere
# Search for similar patterns in codebase
Create PR
git commit -m "fix(scope): description
Closes #<issue>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>"
gh pr create --title "fix(scope): description" --base main
pnpm lint && pnpm typecheck && pnpm test passesmain without the fixOperating manual for documentation work in nexus-agents. Use when updating docs, adding new docs, changing doc pipeline, or troubleshooting doc issues. Triggers on "update docs", "add documentation", "doc pipeline".
Periodically exercise ALL nexus-agents feature families end-to-end against a real task — research → synthesize → vote → plan → dev-pipeline → graph workflow → memory → audit — capturing ACTUAL outputs to validate that fixes, docs, and claims hold in real usage (the things unit tests miss: live voter panels, adapter routing, pipeline stage wiring, audit chains). Use after a release, weekly, when several fixes have landed since the last run, or on demand. Triggers on "e2e validation", "end-to-end validation", "dogfood the loops", "validate end to end", "real usage test", "periodic validation run", "full-loop validation".
Run the CI gates locally before pushing, so failures surface in seconds instead of one CI cycle at a time. Enumerates the checks in .github/workflows/, runs the locally-runnable subset in CI's order, and pins the local-vs-CI delta as a memory the first time you work in a repo. Use before `git push` / opening a PR, or when CI just failed on something your local gate missed. Triggers on "pre-push", "before push", "ci parity", "will ci pass", "local gate", "prepush", "pre-push check".
Review code changes following project standards and security guidelines. Checks for lint compliance, type safety, test coverage, and security issues. Use when reviewing PRs, auditing code, checking implementation quality, or running a blind pre-merge review pass before merging your own change. Triggers on "review code", "code review", "check this", "audit", "PR review", "pre-merge review", "blind reviewer", "before merge".
Execute a release following project standards. Use when publishing a new version, creating release tags, or deploying. Triggers on "release", "publish", "version bump", "create release".
Improve an existing technical doc in-place via a phased Audit → Research → Rewrite → Validate workflow. Calls docs-review for audit and validate; never re-derives scoring. Applies answer-first H2s, citation capsules, and info-gain markers per .rules/docs-rubric.md. Use when the user says "rewrite docs", "improve this doc", "optimize doc", "docs rewrite".