Run structured code review workflows for Git feature branches before merge.
npx skills add https://github.com/nodatall/primedirective --skill review-chain
Please help me install this Agent Skill. Skill: review-chain Source: https://github.com/nodatall/primedirective/tree/main/skills/review-chain Command: npx skills add https://github.com/nodatall/primedirective --skill review-chain
This Skill eliminates the risk of missed defects and compliance gaps in branch code reviews by enforcing a structured, consistent workflow that catches boundary violations, contract mismatches, and edge case oversights before code is merged to main.
Use the review-chain skill to run a full ad-hoc review of your current feature branch against the main branch.
High-intent search queries and answers about installing and using this skill.
Run a structured code review on a Git feature branch by executing explicit workflows that catch defects and compliance gaps prior to merge. This enforces standardized protocols including architecture compliance checks and finding disposition tracking.
Task-scoped branch review aligns code review checks with specific task requirements, PRDs, and task contracts. Use it when you have task artifacts available and need to verify that feature branch code changes satisfy specific project requirements before merge.
Yes, you can optionally preserve review logs and findings as audit-ready artifacts during branch code reviews. This supports compliance tracking and provides post-review reference for unresolved TODOs and test coverage gaps.
Yes, branch review workflows enforce architecture compliance checks and completion gate validation for unresolved TODOs and test coverage gaps. This catches architecture drift, missing test coverage, and security gaps before code is merged to main.
The best way to catch architecture drift and contract mismatches is running a full ad-hoc branch review that enforces reasoning budget adherence and standardized review protocols. This catches edge case oversights and boundary violations before code merge.
No, you do not need task contracts or PRDs to run a code review. You can perform ad-hoc full-branch reviews for general code changes without requiring task-specific context, though task-scoped reviews offer deeper alignment when artifacts are available.
Himanshu040604Verify tests, then merge, create a pull request, or discard a Git branch.
nodatallAutomate branch merge-readiness reviews against the main branch diff.
Luis-ERPValidate phase progression and artifacts against the canonical WORKFLOW.md.
frogguguguguReview code changes for quality, conventions, performance, and security.
