code-review

Solid

Review an implementation slice against the actual diff, approved design and delivery packages, tests, and validation evidence, then record findings or a clean first-pass review. Use after implement hands off a milestone or when implementation review is requested. Use design-review, delivery-review, verify, or pr for those gates instead.

Code & Development 3 stars 0 forks Updated today MIT

Install

View on GitHub

Quality Score: 82/100

Stars 20%
20
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Independent implementation review ## Test criteria application When the project explicitly adopts Test-model criteria, use the selectively loaded guidance below for test quality and maintenance. These criteria replace source-local shared test-purpose, case-selection and maintenance criteria for adopted work; retain specialist methods and historical procedures. Actual judgments, evidence applicability and closeout consequences remain with the responsible assessors under the project's review policy. ## Quick operating guide Use this skill to: inspect the actual review surface against its governing contract and record a first-pass review outcome. Read first: the actual diff, tracked governing authority, current milestone, relevant tests, and validation evidence. Produce: a recorded review status, findings or no-finding rationale, checklist coverage, and milestone-aware handoff. Stop when: authority, evidence, or milestone state cannot support a credible outcome, or an owner decision is required. Do not claim: branch-ready, PR-ready, verification passed, CI passed, or fixes owned by another stage. Next stage: review-resolution for findings, the next milestone after a clean non-final review, or final closeout after the required final holistic review. Use broader-section or full-file reading when bounded evidence is insufficient. ## Review and Closeout application When project authority explicitly adopts Review and Closeout policy, use the packaged application below f...

Details

Author
xiongxianfei
Repository
xiongxianfei/rigorloop
Created
4 months ago
Last Updated
today
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Solid

implement

Implement one approved milestone or isolated implementation request with tests or proof first, then hand it to code-review with validation evidence. Use when requirements, scope, and validation commands are clear enough to code. Use bugfix for defect reproduction/fix loops, code-review to review implementation, verify for final readiness, and pr for PR handoff.

3 Updated today
xiongxianfei
Code & Development Listed

code-review

Use for source-read-only review of a PR, diff, commit, migration, refactor, or implementation through its dependency cone. Not for root-cause diagnosis, authorised fixes, or browser/UX review; use diagnose, implement, or ui-ux-design.

1 Updated yesterday
mblauberg
Code & Development Listed

code-review

Use when the user wants a code review of a branch, PR, MR, or working diff against its acceptance criteria and declared scope, in whatever form they take in this repo. Triggers on "review my branch", "review this PR", "check this diff before I raise it", "is this ready to merge". Works with any language, delivery process, or issue tracker. Produces a structured verdict with blocking, warning, and suggestion findings; writes no source changes. Do NOT use to address or fix review findings (code-review-fix), to implement work (implement), to publish a review to a provider as its reviewer (merge-request-review), to sign off completion of a larger body of work (validate), or to review rendered UI (ux-design-review).

2 Updated 3 weeks ago
carinyaparc