Skip to content
Skills Library
Programming · Review & audit

code-review-completeness

/code-review-completeness

Review a PR through the CodeReviewCompleteness persona. Use when asked to check whether a PR fully addresses the objectives it claims to address in its title, description, cited issue, PRD, epic, acceptance criteria, or linked discussion.

Repository
moraine ↗
Licence
Apache-2.0
Last repository change
10.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 10.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Review a PR through the CodeReviewCompleteness persona. Use when asked to check whether a PR fully addresses the objectives it claims to address in its title, description, cited issue, PRD, epic, acceptance criteria, or linked discussion.

Original author description

Review a PR through the CodeReviewCompleteness persona. Use when asked to check whether a PR fully addresses the objectives it claims to address in its title, description, cited issue, PRD, epic, acceptance criteria, or linked discussion.

How it works

  1. Persona
  2. Focus
  3. Non-Goals
  4. Output
Original SKILL.md headings · 32 lines, 191 words
SKILL.md preview
---
name: code-review-completeness
description: Review a PR through the CodeReviewCompleteness persona. Use when asked to check whether a PR fully addresses the objectives it claims to address in its title, description, cited issue, PRD, epic, acceptance criteria, or linked discussion.
---

# CodeReviewCompleteness

## Persona

Review against the stated objective. Compare the PR's claims with the diff, tests, docs, and linked artifacts, then identify missing pieces that prevent the PR from actually satisfying its own contract.

## Focus

- Extract the promised objectives from the title, PR body, issue, PRD, epic, acceptance criteria, or linked discussion.
- Check whether each promised behavior is implemented, documented, and validated.
- Identify missing config, docs, migrations, tests, fixtures, telemetry, release notes, or operational steps required by the claim.
- Distinguish incomplete promised work from unrelated nice-to-have follow-up work.
- Flag vague PR descriptions that make completeness impossible to verify.

## Non-Goals

Do not expand the PR's scope beyond its stated objective. Do not require unrelated improvements merely because you noticed them.

## Output

Lead with missing objective coverage:

```markdown
- [P1] Add the documented MCP behavior test
  `docs/example.md:31`
  The PR claims `project_only` search now filters every MCP tool, but the diff
  only tests `search_sessions`. Add coverage for `open` or narrow the PR claim.
```

If the PR satisfies its stated objectives, say the stated objectives are covered and mention any assumptions about missing external artifacts.
Files in this package (2)
  • SKILL.md 2 KB
  • agents/openai.yaml 1 KB

Versions

The database has no other skills named code-review-completeness.

Database snapshot: 13.11.2026 · package version f70aca2b5f63 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90audit-completeness
    Audits the codebase to verify every PRD feature is fully implemented, not just scaffolded. This skill should be used when the user asks to "audit implementation completeness", "check for stubs", "detect stub components", "run implementation audit", "run Stage 5B", "verify…
  • 100acceptance-check
    Standalone acceptance check — validates AC from PRD against code without full /implement pipeline. Use when the user says "check acceptance", "validate AC", "verify acceptance", "acceptance gate", or needs to verify acceptance criteria for a PR or external contribution.
  • 90qa-prd
    Independently QA an implemented PRD against its issue spec before sign-off — verify acceptance criteria, required tests, user-story coverage, and out-of-scope guarantees against the real merged code, then post a sign-off comment. Use when the user wants a QA pass on delivered…
  • 100review-pr
    Review a pull request for code quality and security issues. Use when the user wants to review a PR, check PR code changes, or audit a pull request. Triggers on: "review PR", "review pull request", "check this PR", "the `review-pr` skill".
  • 90implement-task
    Implements an agreed task from a local Markdown plan, GitHub Issue, or Jira ticket, checking dependencies and linked requirements, making scoped changes, and validating acceptance criteria. Use when asked to work on, execute, or implement a planned task and prepare it for review.
  • 100review-prd
    Review an existing PRD for completeness, quality, and anti-patterns when the user asks to review, critique, or check a PRD

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.