Review pull requests against a multi-dimensional readiness checklist before merging.
npx skills add https://github.com/Xipher-Labs/walter-os --skill pr-review-xipher-labs
Please help me install this Agent Skill. Skill: pr-review Source: https://github.com/Xipher-Labs/walter-os/tree/main/skills/pr-review Command: npx skills add https://github.com/Xipher-Labs/walter-os --skill pr-review-xipher-labs
It eliminates risky PR merges by ensuring every pull request is checked against a rigorous, multi-dimensional quality and readiness rubric before it enters the mainline.
Use pr-review to evaluate the pull request diff for merge readiness by asking the AI: "Review this PR for correctness, security, performance, testing rigor, readability, backward compatibility, and operational risks, and highlight blocking findings."
High-intent search queries and answers about installing and using this skill.
Automated pull request reviews use a checklist-based rubric to evaluate correctness, security, performance, and testing rigor before merging. This validates PR title conventions, spec alignment, and backward compatibility while explicitly blocking merges when critical findings are detected.
CI quality gates and test rigor are enforced by applying a multi-dimensional readiness rubric across branch promotion scenarios. This verifies that acceptance criteria map to tests, checks lint and typecheck status, confirms no debug artifacts exist, and ensures review iterations stay within defined limits.
Checklist-driven code review prevents unsafe merges by validating PR readiness against explicit blocking criteria before code enters the mainline. It checks for secrets, enforces title and plan alignment, and scores operational readiness to ensure no risky code bypasses the review process.
PR readiness can be validated before opening a pull request by running a pre-opening review. This checks spec and plan alignment, verifies tests and typechecks pass, and confirms no debug artifacts or secrets are present to ensure the PR is ready for review.
A code review checklist for backward compatibility and operational readiness should validate spec alignment, test rigor, and performance. It must confirm acceptance criteria map to tests, check for debug artifacts, and use an explicit blocking findings template to flag critical issues.
Pull requests fail merge readiness checks despite passing tests when they violate non-functional requirements. The review catches missing spec alignment, insufficient test rigor for acceptance criteria, backward compatibility risks, or operational readiness gaps that basic test suites do not cover.
dan1901Validate Spec-Driven Development artifacts across feature directories and generate a report of findings and recommendations.
jassicsReview and secure CI/CD pipelines with automated security scanning gates.
abdullah1854Develop evaluation frameworks for non-deterministic agent systems.
fabioc-alohaReduce Markdown lint errors by enforcing formatting rules during authoring.
