メニュー
Post-op check for artifacts, damage, and stale references after agent work
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | sweep |
| description | Post-op check for artifacts, damage, and stale references after agent work |
Audit the working tree after agent work completes. Find what the agents left behind.
Map every file touched, across all repos affected:
git diff --stat
git diff --cached --stat
If other repos were modified (check recent tool output or plan files for cross-repo work), run git diff --stat there too.
Flag anything unexpected — files not mentioned in the plan or task.
Check whether test fixtures, example files, seed data, or sample configs were modified:
example, fixture, seed, sample, mock, test-dataSearch for references that became outdated by the work:
Scan for artifacts agents leave behind:
console.log, print(), echo "DEBUG" statements*.tmp, *.bak, /tmp/ references)Identify changes outside the task scope:
If plan files exist for the work just completed, check acceptance criteria:
Present findings as a short checklist:
Be terse. Name files and line numbers. Skip categories with no findings.
Review what agents accomplished, surface loose ends across sessions
Reflect on recent work—capture learnings and surface what to think about next
Survey the project and choose what to play next
Create Excalidraw diagrams programmatically. Use when the user wants architecture diagrams, system designs, flowcharts, or any visual diagram with a hand-drawn aesthetic. Outputs editable .excalidraw JSON files. Best for architecture overviews and presentations where the hand-drawn style and drag-and-drop editing add value over Mermaid's text-only approach.
Create diagrams and visualizations using Mermaid.js v11 syntax. Use when generating flowcharts, sequence diagrams, class diagrams, state diagrams, ER diagrams, Gantt charts, user journeys, timelines, or any of 24+ diagram types. Supports CLI rendering to SVG/PNG/PDF, theming, and configuration. Essential for inline documentation diagrams that render natively on GitHub.
Judgment linter for vibe-coded output — reads the energy of the code, not just correctness. Use when the user says "vibe check", "check this vibe code", "does this hold up", "sanity check this AI code", or after a fast generation session before committing.