reviewing-code

Review code against project rules and write findings to a markdown file.

1|Updated Apr 12, 2026

Search Tags:#checklist #traceability #quality-assurance #code-review #software-engineering #project-rules #review-report

Ready to run

npx skills add https://github.com/fascari/ai-config --skill reviewing-code-fascari

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: reviewing-code
Source: https://github.com/fascari/ai-config/tree/main/skills/reviewing-code
Command: npx skills add https://github.com/fascari/ai-config --skill reviewing-code-fascari

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It enables teams to perform thorough code reviews that verify compliance with project rules and ensure traceability to requirements, without making code changes.

Core Features & Use Cases

Performs comprehensive code reviews against project-wide rules and conventions.
Categorizes findings as BLOCKER or SUGGESTION and reports them for downstream action.
Performs requirements traceability reviews when an issue-tracker ticket key is provided.

Quick Start

Review a recent code change and generate a findings report that highlights blockers and suggested improvements.

Frequently Asked Questions about reviewing-code

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I perform a code review against project rules without modifying the code?▼

A code review against project rules identifies and reports quality issues without making changes. Findings are categorized as BLOCKER or SUGGESTION and written to a review report file for downstream action.

Can I verify requirements traceability against an issue tracker ticket during a code review?▼

Yes, requirements traceability is verified by providing an issue tracker ticket key. The review reads project instructions and checks the code against the Quality Checklist to ensure traceability to the specified ticket.

What is the best way to generate a code review report that highlights blockers and suggestions?▼

The best way to generate a review report is to run a review that applies the Quality Checklist from project instructions. Results are categorized into BLOCKER or SUGGESTION findings and written to .github/plans/{slug}/reviews/review-{model}.md.

Does code review work with downstream orchestration after implementation is complete?▼

Yes, code review works when orchestrating-tasks delegates the review after implementation. It reads project rules and generates a findings report categorizing blockers and suggested improvements for the orchestrator.

What do I need to provide to get a code quality and traceability review for my project?▼

You need to provide the recent code change and optionally an issue tracker ticket key for traceability. The review applies the project's Quality Checklist and writes the categorized findings to the appropriate review file.