Post-op check for artifacts, damage, and stale references after agent work
60
70%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./skills/sweep/SKILL.mdAudit the working tree after agent work completes. Find what the agents left behind.
Map every file touched, across all repos affected:
git diff --statgit diff --cached --statIf 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.
The post-agent triad: sweep checks for collateral damage, the other two check fidelity and threads.
/debrief: cross-session recap of what agents accomplished and the loose ends/agent-watchdog: audit whether an agent did what was asked, with a gap report and a narrow fix5647baf
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.