How does jp-codereview differ from standard linters?

While linters focus on syntax and style, jp-codereview analyzes architectural logic, security vulnerabilities, and functional alignment with your PRD.

Can I review only the files I've recently modified?

Yes, the skill supports a 'changed' scope argument that uses git diff to focus specifically on files updated since the last review round.

How are issues prioritized in the report?

Issues are categorized by severity levels: CRITICAL for broken functionality/security, MAJOR for architectural issues, and MINOR for code smells or naming.

What documentation is needed to run a review?

The skill requires a directory containing a prd.md (Product Requirements Document) and tasks.yaml to provide the necessary context for the review.

Where does the skill store its findings?

Findings are written to structured YAML files in a versioned cycle directory (e.g., 001.yaml, 002.yaml) within your project's phase directory.

JPlan Holistic Code Review

Name: JPlan Holistic Code Review
Author: jinglemansweep

byjinglemansweep

0•

Security & Testing

Performs comprehensive architectural and security code reviews, generating structured issue reports aligned with project requirements.

The jp-codereview skill provides a systematic approach to code quality by evaluating implementations against their original PRDs and task lists. It focuses on high-impact areas such as integration correctness, architectural consistency, and security vulnerabilities rather than simple stylistic preferences. By generating versioned YAML reports, it allows developers and AI agents to track issues across multiple fix rounds, ensuring that every piece of code is robust, secure, and functionally aligned with the project's goals.

Key Features

01Architectural pattern and dependency flow analysis

02Automated API contract and integration consistency verification

03Structured YAML reporting with severity-based issue classification

040 GitHub stars

05Incremental review support for changed files between fix rounds

06Security auditing for injection, auth gaps, and data exposure

Use Cases

01Identifying critical security flaws and integration gaps before merging complex code changes

02Ensuring new feature implementations strictly adhere to the project's PRD and technical specifications

03Maintaining a structured audit trail of code quality issues and resolutions during iterative development

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add jinglemansweep/agent-resources jp-codereview

For use in Claude.ai and ChatGPT

Key Features

01Architectural pattern and dependency flow analysis

02Automated API contract and integration consistency verification

03Structured YAML reporting with severity-based issue classification

040 GitHub stars

05Incremental review support for changed files between fix rounds

06Security auditing for injection, auth gaps, and data exposure

Use Cases

01Identifying critical security flaws and integration gaps before merging complex code changes

02Ensuring new feature implementations strictly adhere to the project's PRD and technical specifications

03Maintaining a structured audit trail of code quality issues and resolutions during iterative development

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add jinglemansweep/agent-resources jp-codereview

For use in Claude.ai and ChatGPT