skills.rest
islamu-ngo
islamu-ngoOFFICIAL
Explore all skills by this author →
GitHub

review-pr

Validates pull requests against intent checklists, scope rules, tests, and forbidden actions.

7|3|Updated Sep 23, 2025
Search Tags:#code review#checklist#pull request#merge readiness#scope validation#dotnet test#architecture tests
One-click install
npx skills add https://github.com/islamu-ngo/Event --skill review-pr-islamu-ngo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-pr
Source: https://github.com/islamu-ngo/Event/tree/main/.agents/skills/review-pr
Command: npx skills add https://github.com/islamu-ngo/Event --skill review-pr-islamu-ngo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Pull request reviews often miss scope violations, missing tests, or undocumented contract changes. This Skill enforces a structured, evidence-based review process so every PR is verified against its declared intent before merge. ## Core Features & Use Cases - Intent-Driven Checklists: Re-identifies the matching intent in intents.yaml and executes its pr_checklist with required evidence for tests, docs, and rule adherence. - Scope Discipline Gates: Verifies every changed file is inside paths_in_scope, outside paths_forbidden, and that no forbidden_without_approval items trigger without explicit approval. - Verification Evidence: Requires concrete build and test command output (dotnet build, dotnet test, architecture tests) plus a paste-ready review summary. - Use Case: Before opening a PR that changes an API endpoint, run this review to confirm authorization parity tests pass, the API changelog is updated, and no out-of-scope files were touched. ## Quick Start Ask the AI to run the review-pr checklist on your current branch before opening the pull request.

Frequently Asked Questions about review-pr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a pull request against an intent checklist?▼

Re-identify the matching intent in intents.yaml, then execute each item in its pr_checklist and collect evidence such as test output and doc diffs. Any checklist item without evidence blocks the review.

What checks should run before opening a pull request?▼

Fetch the latest upstream, confirm all changed files are within paths_in_scope, run dotnet build and the minimum test project, and verify no forbidden_without_approval items trigger. Finish with the critical rules and documentation sanity checklists.

When must a pull request review fail?▼

The review must fail if any checklist item lacks evidence, any file falls outside paths_in_scope or inside paths_forbidden, a forbidden action triggers without approval, an architecture test fails, or a critical rule is violated.

Does this review process work for general code-quality feedback?▼

No. The Skill explicitly excludes general code-quality diff reviews; it only verifies matched intent, allowed scope, required tests and docs, forbidden actions, architecture gates, and merge readiness.

What evidence is required for architectural changes in a PR?▼

Architectural PRs must run the Event.Architecture.Tests project in Release configuration and show passing output. Contract changes additionally require an entry in docs/internal/API_CHANGELOG.md.

Related Skills

Explore More Software Engineering Skills→
warpdotdevwarpdotdev
292

implement-specs

Plan and execute feature implementations while keeping specs aligned with code changes.

Official
Advanced
highflame-aihighflame-ai
4

release-notes

Generate structured release notes from git commit history and pull requests.

Official
Advanced
tarekBassiounytarekBassiouny

Najaah LMS - Code Quality Agent

Enforces code quality standards for the Najaah LMS project using Pest, PHPStan, and Laravel Pint.

Community
Advanced
kurkokurko
14

code-review

Generate complete verbatim code reviews for pull requests, diffs, and uncommitted Git changes.

Community
Advanced