Skip to content
Skills Library
Programming · Review & audit

mcaf-code-review

/mcaf-code-review

Review a diff for correctness, requirement coverage, test quality, and operational risk, or refine PR review policy and templates. Use for concrete findings and review readiness.

Repository
MCAF ↗
Licence
CC-BY-4.0
Last repository change
11.10.2026

Assessment and security

90/ 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.
Content25 / 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
6
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

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

Licence

CC-BY-4.0, otwarta.

What it does and when to use it

Review a diff for correctness, requirement coverage, test quality, and operational risk, or refine PR review policy and templates. Use for concrete findings and review readiness.

Original author description

Review a diff for correctness, requirement coverage, test quality, and operational risk, or refine PR review policy and templates. Use for concrete findings and review readiness.

How it works

  1. Workflow
  2. References
Original SKILL.md headings · 24 lines, 280 words
SKILL.md preview
---
name: mcaf-code-review
description: "Review a diff for correctness, requirement coverage, test quality, and operational risk, or refine PR review policy and templates. Use for concrete findings and review readiness."
metadata:
  compatibility: "Requires repository access; may update PR templates, review docs, or contribution guidance."
---

# MCAF: Code Review

Follow root and applicable local `AGENTS.md`. A review request authorizes inspection; implementation or external review actions remain within the user's requested scope.

## Workflow

1. Read the complete diff plus affected implementations, callers, contracts, tests, and docs. Identify the accepted requirements and specific risks before judging the change.
2. Check behavior, authorization, state ownership, failure handling, migration, and end-to-end wiring where relevant. Report concrete defects or missing requirements with their trigger, impact, and exact path; do not invent findings to fill a checklist.
3. Review tests before execution: real flows, meaningful outcomes, required negative/edge paths, isolation, and the ability to detect the regression. Passing weak tests is insufficient proof.
4. Apply `MCAF-ARCH-001`: all solution artifacts remain in one repository and affected surfaces use their canonical slice names.
5. Apply `MCAF-REQ-001`: requirements trace through acceptance, required ADR implementation contracts, tasks, tests, and evidence. Reject premature `Verified`/`Implemented` status.
6. For delegated work, apply `MCAF-AI-001`: the lead inspects every diff, ownership and contract compliance, explicit completion states, required joins, and combined verification.
7. Check that material architecture, serialization, contract, data, security, dependency, or deployment decisions have user approval. Existing authorization covers its exact scope.
8. Finish self-review and fixes before planned verification. Repeat a review or check only to resolve a new change, concrete failure, or unanswered risk.

Return actionable findings ordered by impact, then any verification limits. If none exist, say so. For policy work, deliver the requested repo guidance or PR template without imposing an unrelated process.

## References

- For review expectations: [code reviews](references/code-reviews.md) and [PR readiness](references/pull-requests.md).
- When creating a template: [PR scaffold](references/pull-request-template.md).
- When addressing review communication or process friction: [communication](references/inclusion-in-code-review.md) or [review FAQ](references/faq.md).
Files in this package (6)
  • SKILL.md 3 KB
  • references/code-reviews.md 1 KB
  • references/faq.md 1 KB
  • references/inclusion-in-code-review.md 1 KB
  • references/pull-request-template.md 3 KB
  • references/pull-requests.md 1 KB

Versions

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

Database snapshot: 13.11.2026 · package version 87d3ab918643 (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

  • 90mcaf-source-control
    Define or refine branch, merge, commit, release, and repository ownership policy. Use for source-control governance or secrets-in-history response, not routine Git commands.
  • 100code-review
    Reviews pull requests and code changes for correctness, conventions, maintainability, performance, test coverage, and security. Use when the user asks for a code review, PR review, feedback on a diff, or to check code quality.
  • 81ork-review-pr
    Review a pull request or branch for correctness, regressions, security, operational risk, and missing evidence. Use when a request asks to review a PR, review a diff, find real bugs, assess merge risk, or provide evidence-backed review findings. Do not use for implementation or style-only cleanup.
  • 90code-review-and-quality
    Reviews a diff for correctness, risk, and missing evidence before merge. Use when preparing a change for commit, reviewing a pull request, reviewing AI-generated code, or deciding whether work is genuinely done.
  • 90code-review
    Review EF Core pull requests or local changes for concrete correctness, compatibility, performance, security, and test-coverage problems. Use when asked to review, critique, or check code changes before merge or submission.
  • 95pr-review
    Review a PR for correctness, security, code quality, and testing issues. TRIGGER when user asks to review a PR, check PR quality, or give feedback on a PR.

Feedback and reports

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