Turn feature requests into review-ready pull requests: issue, implementation, tests, a review-and-fix loop, and docs. Runs locally or on GitHub Actions, and is built for complex brownfield repos. Each week its retrospective reads what you actually merged and proposes improvements to your skill extensions.
Phase 3.4 claim verifier. Checks the shipped code against each in-scope acceptance criterion's literal claim from the diff and the current tree, in a fresh context, and EXECUTES NOTHING (no verification command, no single-flight). For a verification-command criterion it reads the command's SOURCE and checks each…
Phase 3.4 evidence verifier. Establishes each in-scope acceptance criterion's verification evidence in a fresh context, and is the ONLY verifier that runs an in-env verification command or touches the single-flight coordination. Reports one status per criterion (satisfied | unmet | unestablished) with an evidence…
PRFlow's implement-phase Branch-Setup agent. Runs Phase 1.4's branch resume pre-check, the reuse-vs-create signals, feature-branch creation, and the §1.4.0.5 Verdict-B ahead-of-base classification against the actual repository, records each durable outcome on the workpad, and returns a structured record for the…
Merges multiple batches of checklist items from checklist-generator into a single deduped checklist. Preserves traceability by recording which original IDs were merged. Does NOT judge correctness or re-tag items.
Use when an orchestrator needs to enumerate every verifiable claim in a code diff (dependency interactions, test-mock alignment, data format assumptions, API contracts) and return a JSON checklist for independent verification. Does NOT judge correctness.
Verifies a single claim from the verification checklist against the actual source code. Reports PASS, FAIL, or INCONCLUSIVE with file:line evidence. Used for verificationmode: "agent" items; lite-mode items are resolved by the orchestrator directly via grep.
PRFlow's implement-phase planning agent. Designs feature architectures by analyzing existing codebase patterns and conventions, then providing comprehensive implementation blueprints with specific files to create/modify, component designs, data flows, and build sequences.
PRFlow's implement-phase discovery agent. Deeply analyzes existing codebase features by tracing execution paths, mapping architecture layers, understanding patterns and abstractions, and documenting dependencies to inform new development.
PRFlow's project-guidelines reviewer, dispatched by the review engine and available directly. Use this agent when you need to review code for adherence to project guidelines, style guides, and best practices. This agent should be used proactively after writing or modifying code, especially before committing changes or…
PRFlow's comment-quality reviewer, dispatched by the review engine and available directly. Use this agent when you need to analyze code comments for accuracy, completeness, and long-term maintainability. This includes (1) after generating large documentation comments or docstrings, (2) before finalizing a pull request…
PRFlow's implement-phase Deferral-Drafter agent. Holds the Phase 4.0 follow-up-issue composition procedure. Given the outstanding deferred acceptance criteria, the parent issue body, and the Phase 2.2.5 scope-decision note, it composes the follow-up issue bodies under .prflow/tmp/ and returns a filing plan of those…
PRFlow's implement-phase Issue-Claim Audit agent. Runs Phase 1.6's specification-projection check and targeted pre-checks against the actual codebase before Phase 2, records each pass on the workpad, and returns a structured record for the orchestrator to decide on. Dispatches nothing itself.
PRFlow's test-coverage reviewer, dispatched by the review engine and available directly. Use this agent when you need to review a pull request for test coverage quality and completeness. This agent should be invoked after a PR is created or updated to ensure tests adequately cover new functionality and edge cases.…
PRFlow's silent-failure reviewer, dispatched by the review engine and available directly. Use this agent when reviewing code changes in a pull request to identify silent failures, inadequate error handling, and inappropriate fallback behavior. This agent should be invoked proactively after completing a logical chunk…
PRFlow's type-design reviewer, dispatched by the review engine and available directly. Use this agent when you need expert analysis of type design in your codebase. Specifically use it (1) when introducing a new type to ensure it follows best practices for encapsulation and invariant expression, (2) during pull…