Review Builder changes against Architect pitch for spec compliance and code quality.
npx skills add https://github.com/ddpoe/pev-agent-nexus --skill pev-reviewer
Please help me install this Agent Skill. Skill: pev-reviewer Source: https://github.com/ddpoe/pev-agent-nexus/tree/main/plugins/pev/skills/pev-reviewer Command: npx skills add https://github.com/ddpoe/pev-agent-nexus --skill pev-reviewer
This skill provides a structured, repeatable approach to reviewing code changes against an Architect pitch, capturing compliance, preservation of functionality, and quality concerns without modifying the code itself.
Initiate the review by reading the cycle manifest and running cortex_check to map affected nodes, then proceed with Pass 1.
High-intent search queries and answers about installing and using this skill.
Code review for Builder changes involves a three-pass workflow verifying spec compliance, functionality preservation, and quality. This skill applies the PEV reviewer process across cycle manifests and worktrees, using cortex tools like check and diff to assess changes against the Architect pitch.
The PEV reviewer workflow is a structured process for reviewing code changes against an Architect pitch. It applies a three-pass assessment covering spec compliance, functionality preservation, and quality, persisting review outcomes directly to the cycle manifest via cortex_update_section.
Yes, cortex tooling is required to run these code reviews. The skill leverages cortex_check, cortex_diff, cortex_history, cortex_graph, and cortex_source to map affected nodes, verify diffs, and assess changes across worktrees and cycle manifests.
To persist code review outcomes to a cycle manifest, the skill uses cortex_update_section to write progress and results. This ensures that spec compliance, functionality preservation, and quality assessments are saved as artifacts within the manifest.
Yes, you can verify functionality preservation without modifying the code. The skill acts as a read-only reviewer, applying a three-pass workflow to assess spec compliance, functionality, and quality against the Architect pitch using cortex diff and history tools.
The best way to start a guided code review is to read the cycle manifest and run cortex_check to map affected nodes. From there, proceed with the first pass of the three-pass workflow to verify spec compliance against the Architect pitch.
adiomasCoordinate independent tasks in parallel using isolated git worktrees.
nahisahoAnalyze proposed changes to detect breaking changes and generate impact reports.
jikig-aiTrace code evolution and origins using git log, blame, and shortlog.
JuniYadiAssess software proposals against clean architecture and maintainability criteria.
