Code review
Verify implementation matches requirements from checkpoint intent filesFrom its SKILL.md
npx -y skills add dipasqualew/vibereq --skill code-reviewAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 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
2.5 KB, as published. Nobody here has run it
Code Review
Requirements
The following requirements were captured from checkpoint intent files:
!vibx get-intents
Current Changes
!git --no-pager diff main...HEAD
Your Task
For each requirement from the intent files:
- Status: Fulfilled, Partially Fulfilled, Missing, or Violation
- Evidence: Reference specific code changes that address the requirement
- Issues: Any problems, bugs, or deviations from the requirement
- Recommendations: Concrete fixes for identified issues
Also identify:
- Code that doesn't map to a stated requirement (scope creep)
- Potential bugs or edge cases not handled
- Code quality concerns (error handling, type safety)
Output Format
Check the mode argument:
If mode is "ci":
CRITICAL: Your entire response must be ONLY the raw JSON object below. Do not include:
- Any text before the JSON (no "Based on my analysis...", "Here is the output:", etc.)
- Any text after the JSON
- Markdown code fences (
json or) - Any commentary or explanation
Start your response with { and end with }. Nothing else.
JSON structure: { "status": "pass" | "fail" | "warn", "summary": "Brief one-line summary", "findings": [ { "requirement": "What was expected", "status": "fulfilled" | "partial" | "missing" | "violation", "severity": "critical" | "major" | "minor" | "info", "location": { "file": "path/to/file.ts", "line": 42, "endLine": 45 } | null, "details": "Explanation with evidence and recommendations" } ] }
Notes on the location field:
- Set
locationto an object withfileandlinewhen the finding relates to a specific code location endLineis optional, use it for multi-line findings- Set
locationtonullfor general findings not tied to specific code (e.g., missing functionality) - The
filepath must be relative to the repository root - The
linemust be within the diff range for the file (changed lines only)
If mode is not "ci" (default):
Output a human-readable markdown report with:
- Summary of findings
- Detailed analysis per requirement
- Specific file:line references for issues
- Concrete recommendations