post-merge-scan

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

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

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

Quality

Content

72%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tight, well-structured instruction skill that respects the context budget, but its guidance is more descriptive than executable and lacks validation checkpoints around the auto-fix step. Tightening the output spec and adding a verify step would lift the weaker dimensions.

Suggestions

Specify the exact format/content of the prioritized list in `post-merge-state.md` (e.g., columns or fields per item) so output is reproducible.

Add an explicit validation/verification checkpoint before and after any auto-fix attempt (e.g., re-run lint/tests, confirm the fix applies) since auto-fix is a batch operation.

Give concrete commands for the scan steps beyond `git diff HEAD~10` (e.g., how to enumerate recent merged PRs or surface introduced lint warnings).

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — short bullet lists with no conceptual padding — so every token earns its place.	3 / 3
Actionability	It gives some concrete specifics (`git diff HEAD~10`, `post-merge-state.md`) but mostly describes tasks rather than instructing; the output format and how to produce the prioritized list are underspecified.	2 / 3
Workflow Clarity	Sections imply a scan → classify → output sequence, but there are no explicit validation checkpoints, and auto-fix is a batch/destructive-style operation where missing verification caps clarity at 2.	2 / 3
Progressive Disclosure	This is a simple under-50-line skill with no need for external references, and its sections (Scan Sources, Classification, Output, Rules) are well organized — meeting the simple-skill allowance for a 3.	3 / 3
	Total	10 / 12 Passed

Description

67%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A specific, lean description that names concrete scan targets and a clear output, but it omits any explicit 'when to use' trigger guidance. Adding a Use-when clause would raise completeness and trigger-term quality.

Suggestions

Append a 'Use when...' clause stating when Claude should invoke this skill (e.g., after merges land on main, or when the user mentions post-merge cleanup or tech-debt triage).

Add common natural trigger variants such as 'post-merge cleanup', 'tech-debt scan', or 'leftover TODOs' to broaden trigger-term coverage.

Confirm third-person voice is consistent — currently fine, but ensure no first/second-person phrasing creeps in.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions — 'Scan recent merges to main for tech debt, TODOs, debug code, and small cleanup opportunities' and 'Produces a prioritized fix list' — matching the anchor for listing several specific actions.	3 / 3
Completeness	It clearly states what the skill does, but provides no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	It surfaces relevant natural keywords ('tech debt', 'TODOs', 'debug code', 'merges to main', 'cleanup'), but coverage of common phrasings is limited and it lacks the conversational trigger variants a user might say.	2 / 3
Distinctiveness Conflict Risk	The 'recent merges to main' / post-merge cleanup niche is a clear, distinct scope unlikely to trigger for unrelated skills.	3 / 3
	Total	10 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: cobusgreyling/loop-engineering
Path: starters/post-merge-cleanup-opencode/skills/post-merge-scan/SKILL.md
Commit: ffa5bf8

Reviewed: 9 days ago

Table of Contents

Discovery Implementation Validation

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.