Revisar pr
Skill adriannoes/awesome-agentic-ai/cursor-claude-codex/skills/igoruehara-spec-driven/skills/revisar-pr
Use to review a PR/MR against the SDD standard — it checks process conformance: an approved spec for the change, each AC-N with a green test, no open SPEC_DEVIATION, ADRs for irreversible decisions, glossary/context-map updated, and the DoD met. Posts the result as a comment on the PR/MR via the GitHub/GitLab MCP (if connected). Complements the harness /code-review (which hunts for bugs). Trigger with /revisar-pr.From its SKILL.md
npx -y skills add adriannoes/awesome-agentic-ai --skill revisar-prAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
2.5 KB, 520 tokens by cl100k_base, as published. Nobody here has run it
Translation note: Originally authored in Portuguese (pt-BR) by Igor Uehara (igoruehara/spec-driven, MIT). Translated to English by this hub to keep the repository language consistent. Original content unchanged in meaning; see the upstream repo for the pt-BR source.
Skill: Review PR/MR (SDD conformance gate)
It checks the process, not the bugs. For bugs/quality, use the harness /code-review — this skill verifies that the change respects the SDD pipeline before merging. The two complement each other.
Identify the target
- The PR/MR (number/branch) and the corresponding
specs/NNNN-<name>/feature. - If the GitHub/GitLab MCP is connected (validated account — see
/integracoes), read the diff and metadata through the MCP. If there is no git host MCP, offer to run/integracoesto connect (it enables reading metadata and posting the verdict on the PR/MR); if declined, proceed with the local diff (git diff <base>...HEAD).
SDD conformance checklist
- Spec exists and is approved for the change's scope (correct tier for the size/risk).
- Traceability: every touched
AC-Nhas a test; the diff includes the tests covering the ACs. - Green gates: the commands in
docs/engineering/TESTING.mdpass (or CI is green). - No
SPEC_DEVIATIONopen without resolution. - ADRs recorded for hard-to-reverse decisions introduced in the PR.
- Living docs: glossary/context-map updated if the language/boundaries changed.
- Scope: nothing from the spec's "Out of scope" was implemented; the change is cohesive (one purpose).
- STATE.md updated, if the next step changed.
Verdict
- A clear result: approve or changes requested (list of what is missing, with a link to spec/AC).
- If the GitHub/GitLab MCP is connected and validated, offer to post it as a comment on the PR/MR
(outward-facing — confirm first; reconfirm account/workspace, see
/integracoes). - Suggest running
/code-review(harness) for the bug/quality layer.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.