メニュー
Run a system review to check project health. Use when issues drop below 5, an EPIC closes, or 7+ days since last review. Triggers on "system review", "project health", "review system".
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Operating 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".
| name | system-review |
| description | Run a system review to check project health. Use when issues drop below 5, an EPIC closes, or 7+ days since last review. Triggers on "system review", "project health", "review system". |
| allowed-tools | Read, Edit, Write, Bash, Grep, Glob, Task, WebSearch |
Run when ANY occur:
epic)# Count techniques by status
grep -c "status: implemented" docs/research/registry/techniques.yaml
grep -c "status: planned" docs/research/registry/techniques.yaml
# Verify RESEARCH_INDEX.md matches actual counts
# Check integration_files exist for implemented techniques
gh issue list --state open --limit 50
wontfix label)Create GitHub issue titled "System Review: YYYY-MM-DD" with findings and action items.
TZ='America/New_York' date '+%Y-%m-%d'
gh issue create --title "System Review: $(TZ='America/New_York' date '+%Y-%m-%d')" \
--label "maintenance" --body "## Findings\n\n[report here]"
| Excuse | Counter |
|---|---|
| "Skip the review, I just looked at this last week" | A week is enough for new alerts, dep advisories, and CI flakes. Run all phases. |
| "No new issues, the review is wasted time" | The review's value isn't in finding new issues — it's in confirming the system isn't drifting silently. Empty reviews are good signal. |
| "I'll skip Phase X, it's never useful" | If a phase is never useful, file an issue to remove it. Don't silently skip — the next reviewer will skip a different phase. |