Review pull request diffs against CONTEXT.md principles with severity-tagged findings.
npx skills add https://github.com/ysuurme/azure_hello_world --skill review-ysuurme
Please help me install this Agent Skill. Skill: review Source: https://github.com/ysuurme/azure_hello_world/tree/main/.agents/skills/review Command: npx skills add https://github.com/ysuurme/azure_hello_world --skill review-ysuurme
This Skill prevents architectural drift and defects from reaching main by running a structured PR review cycle with automated fixes when findings are actionable.
Use this Skill when you have an open pull request ready for review and want an enforced, standard-aware review that can automatically fix issues or block with HITL escalation if needed.
High-intent search queries and answers about installing and using this skill.
Automated pull request reviews prevent architectural drift by validating PR diffs against architecture standards using severity-tagged findings. The review process applies auto-fix loops in an isolated worktree and blocks merges when unresolved violations are detected.
When a PR review finds a BLOCK or WARN issue, an auto-fix loop attempts automated correction in an isolated worktree with test verification. If the finding remains unresolved after three iterations, it triggers a human-in-the-loop escalation.
Continuous integration handles unresolved architectural violations by blocking the merge gate and escalating with a human-in-the-loop comment and label. This severity-gated mechanism ensures defects never reach the main branch without manual review.
You can auto-fix code review findings without merging broken code by applying corrections in an isolated worktree. The system verifies fixes with tests and re-evaluates the specific finding before allowing the pull request to become PR-ready.
A human-in-the-loop escalation gate for code reviews is needed when automated auto-fix loops fail to resolve a BLOCK or WARN finding within three iterations. It stops the automated process and blocks the merge until manual intervention occurs.
The PR review process supports severity-gated merge blocking by tagging findings as BLOCK, WARN, or INFO. It blocks the downstream ship gate for any unresolved BLOCK or WARN issues and compacts related findings into a clear review outcome.
uoyoCsharpReview code changes for defects, standards, architecture, and test coverage.
rkz91Push a feature branch, create a pull request with an auto-generated body, and track merge status.
beratcelik1Orchestrate autonomous Claude Code loops for multi-agent pipelines and continuous iterations.
takaokanbeOrchestrate parallel PR review workflows with finding triage, automated fixes, and CI monitoring.
