Compare HEAD against a fixed point to review code standards and spec alignment.
npx skills add https://github.com/tonomb/personal-pnl --skill code-review-tonomb
Please help me install this Agent Skill. Skill: code-review Source: https://github.com/tonomb/personal-pnl/tree/main/.agents/skills/code-review Command: npx skills add https://github.com/tonomb/personal-pnl --skill code-review-tonomb
This skill solves the problem of inconsistent code quality and scope creep by providing a structured, two-axis review process that evaluates code against both technical standards and functional requirements.
Ask the agent to review the changes since the main branch by providing the branch name or commit hash as the fixed point.
High-intent search queries and answers about installing and using this skill.
To perform a dual-axis code review, compare the current HEAD against a fixed branch name or commit hash. This evaluates technical quality and requirement fulfillment independently to ensure adherence to coding standards and functional specifications.
Dual-axis code review is a mechanism that spawns parallel sub-agents to independently analyze technical quality and spec alignment. It verifies implementation against originating issues, PRDs, or specs to identify missing requirements and scope creep.
Yes, this code review process requires git access to resolve references and compare code changes. It checks for code smells by analyzing diffs against documented repository standards and Fowler's Refactoring principles.
The best way to check work-in-progress changes is to provide the main branch name as the fixed point for comparison. The process analyzes the diff to ensure the code is clean and functionally correct before merging.
You need to evaluate diffs for scope creep and missing requirements when reviewing complex pull requests or work-in-progress changes before merging. This ensures the implementation matches the originating issue, PRD, or functional spec.
Yes, static analysis is used to verify implementation against a PRD by spawning parallel sub-agents. One axis checks technical quality against coding standards while the other verifies functional requirement fulfillment independently.
FrantssCompare git diffs against repository standards and project specifications.
huachengMerge completed task branches into main with automated conflict resolution and verification.
barikata1984Automates git-based code quality reviews for commits and pull requests.
CaptainCrouton89Evaluate code changes for security, correctness, performance, and spec alignment.
