Skip to content
Back to skills

Lookagain Output Format

ASecurity

Defines the standard output format for code review findings. Use when performing code reviews to ensure consistent, parseable output.

  • 10 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added February 7, 2026
code-qualityrefactoringapisecurityperformancedocumentation

Works with

  • api

Security analysis

A100/100

Scanned February 12, 2026

npx -y skills add HartBrook/lookagain --skill lookagain-output-format --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Lookagain Output Format?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Lookagain Output Format
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/hartbrook-lookagain-output-format/badge)](https://www.skillsdirectory.com/skills/hartbrook-lookagain-output-format)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: lookagain-output-format
description: Defines the standard output format for code review findings. Use when performing code reviews to ensure consistent, parseable output.
---

# Code Review Output Format

When performing code reviews, output findings in this exact JSON structure:

```json
{
  "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 `null` for optional fields (like `line`) when not applicable
- Keep titles concise and descriptive
- Make suggested_fix actionable

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…