Lookagain output format
Skill HartBrook/lookagain/src/skills/lookagain-output-format
Defines the standard output format for code review findings. Use when performing code reviews to ensure consistent, parseable output.From its SKILL.md
npx -y skills add HartBrook/lookagain --skill lookagain-output-formatAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 10 stars10 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.3 KB, 260 tokens by cl100k_base, as published. Nobody here has run it
Code Review Output Format
When performing code reviews, output findings in this exact JSON structure:
{
"pass_summary": "string - Brief summary of review scope and key findings",
"issues": [
{
"severity": "must_fix | should_fix | suggestion",
"title": "string - Brief title (max 100 chars)",
"description": "string - Detailed explanation of the issue",
"file": "string - Relative file path",
"line": "number | null - Line number if applicable",
"suggested_fix": "string - How to fix it"
}
]
}
Severity Definitions
must_fix:
- Security vulnerabilities
- Bugs causing runtime errors
- Data loss/corruption risks
- Breaking API changes
should_fix:
- Performance issues
- Poor error handling
- Missing edge cases
- Maintainability concerns
suggestion:
- Minor refactoring
- Documentation gaps
- Style improvements
Rules
- Output ONLY valid JSON (no markdown wrapper)
- Include all fields for each issue
- Use
nullfor optional fields (likeline) when not applicable - Keep titles concise and descriptive
- Make suggested_fix actionable
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.