review-changes
Review Git Changes Against Plans
Code changes can drift from plans, miss acceptance criteria, or introduce avoidable defects. This skill guides Claude, Codex, and Claude Code through structured diff review and merge-readiness checks.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "review-changes" from https://skillstore.io/skills/cygnusfear-review-changes.md and its manifest at https://skillstore.io/api/skills/cygnusfear-review-changes/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "review-changes". Review my staged changes before I commit.
Expected outcome:
The review reports one high-priority validation gap, two medium maintainability issues, and a request-changes recommendation.
Using "review-changes". Check this implementation against the plan.
Expected outcome:
The report lists plan matches, missing requirements, scope creep, and required fixes before approval.
Using "review-changes". Audit the branch for release readiness.
Expected outcome:
The summary separates must-fix defects from optional cleanup and explains the final merge recommendation.
Security Audit
SafeI reviewed SKILL.md and found that the static external-command matches are Markdown fences, inline code, file paths, and sample report text. The skill uses git and optional GitHub issue lookup for code review context, with no evidence of injection, exfiltration, or privilege escalation intent.
Risk Factors
⚙️ External commands (49)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/cygnusfear-review-changes/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/cygnusfear-review-changes?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/cygnusfear-review-changes?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/cygnusfear-review-changes/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/cygnusfear-review-changes.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
Cygnusfear. (2026). review-changes security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/cygnusfear-review-changes/audits/8BibTeX citation
@techreport{cygnusfear-cygnusfear-review-changes-2026,
author = {Cygnusfear},
title = {review-changes security audit report (audit version 8)},
institution = {Skillstore},
year = {2026},
number = {8},
url = {https://skillstore.io/skills/cygnusfear-review-changes/audits/8},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "review-changes security audit report (audit version 8)"
version: "unspecified"
type: report
authors:
- name: "Cygnusfear"
date-released: "2026-07-05"
url: "https://skillstore.io/skills/cygnusfear-review-changes/audits/8"
identifiers:
- type: other
value: "skillstore:cygnusfear-review-changes:audit:8"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Pre-Commit Review
Review uncommitted changes before asking for teammate feedback or opening a pull request.
Plan Compliance Check
Check whether an implementation matches an approved plan, including required removals and scope boundaries.
Release Readiness Review
Verify task coverage and required fixes before approving a release branch or merge candidate.
Try These Prompts
Review my current git changes. Compare them to any related plan if one is obvious, then list findings by severity.
Review these changes against the plan in .plans/<plan-name>. Focus on missing requirements, scope creep, and removal requirements.
Use the referenced issue and current diff to build a requirements checklist. Mark each item implemented, partial, or missing with evidence.
Run a full code review for the current branch. Include cross-file risks, architectural drift, severity counts, and a final merge recommendation.
Best Practices
- Provide the relevant plan, issue number, or acceptance criteria before requesting the review.
- Ask for staged, unstaged, or full working tree scope explicitly.
- Review the generated findings before acting on severity recommendations.
Avoid
- Using the skill as an automatic approval gate without human review.
- Running it without sharing the plan or task context for requirement-heavy work.
- Asking it to edit code files during the review flow.
Frequently Asked Questions
Does this skill change my code?
Can it review staged and unstaged changes?
Does it require a plan file?
Can it use GitHub issues?
What output should I expect?
Is it suitable for pull request review?
Developer Details
Author
CygnusfearLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
7e9e368dc1a370f2040369ebcd0db06d90cb48e5
Maintenance freshness
7/18/2026
Usage
4 downloads · 280 views
File structure
📄 SKILL.md