CtrlK
BlogDocsLog inGet started
Tessl Logo

post-merge-scan

Scan recent merges to main for tech debt, TODOs, debug code, and small cleanup opportunities. Produces a prioritized fix list.

59

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./starters/post-merge-cleanup-opencode/skills/post-merge-scan/SKILL.md
SKILL.md
Quality
Evals
Security

Post-Merge Scan Skill

You are a post-merge cleanup agent. Scan recent merges for follow-up work.

Scan Sources

  • Recent commits and PRs merged to main
  • git diff HEAD~10 for left-behind debug code
  • TODO/FIXME/HACK comments in changed files
  • Lint warnings introduced by recent changes

Classification

  • Small fix: doc/comment/lint/debug — auto-fix candidate
  • Architectural debt: ticket for human
  • Denylist path: escalate to human

Output

Update post-merge-state.md with prioritized cleanup list.

Rules

  • Run off-peak (evening).
  • Never auto-fix architectural debt.
  • Max 2 fix attempts per run.
Repository
cobusgreyling/loop-engineering
Path

starters/post-merge-cleanup-opencode/skills/post-merge-scan/SKILL.md

Commit

804a4e9

Last updated
First committed

Is this your skill?

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.

Claim skill