Skills fix-review

📦

fix-review

Name: fix-review
Author: sickn33

Content revision r1 Safe 🌐 Network access

Verify Security Fix Reviews

Security fixes can miss root causes or introduce regressions. This skill guides Claude, Codex, or Claude Code through structured fix validation.

Supports: Claude Codex Code(CC)

🥉 77 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "fix-review" from https://skillstore.io/skills/sickn33-fix-review.md and its manifest at https://skillstore.io/api/skills/sickn33-fix-review/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.

Markdown detail GET /skills/sickn33-fix-review.md Signed manifest GET /api/skills/sickn33-fix-review/manifest Signed lockfile GET /api/skills/sickn33-fix-review/lockfile

Test it

Using "fix-review". A pull request claims to fix an authorization bypass in an API endpoint.

Expected outcome:

The review states whether the authorization check covers all affected paths, then lists test gaps and residual risk.

Using "fix-review". A commit sanitizes user input after a stored cross-site scripting finding.

Expected outcome:

The review explains whether output encoding and stored data handling are complete, then identifies any similar sinks nearby.

Using "fix-review". A patch changes error handling after a secret disclosure finding.

Expected outcome:

The review confirms whether sensitive data is removed from responses and logs, then notes regression tests to add.

Security Audit

Safe

v4 • 7/6/2026 Open versioned report

The skill is prompt-only and contains no executable code, scripts, or tool automation. The two static network findings are source repository links in documentation, not network access behavior.

Files scanned

Lines analyzed

Review items

False positives ignored

Risk Factors

🌐 Network access (2)

SKILL.md:4 SKILL.md:53

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

Audited by: codex View Audit History →

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.

Open versioned report

Copy report link

https://skillstore.io/skills/sickn33-fix-review/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sickn33-fix-review/security.svg)](https://skillstore.io/skills/sickn33-fix-review?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sickn33-fix-review?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-fix-review/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-fix-review.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

sickn33. (2026). fix-review security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-fix-review/audits/4

BibTeX citation

@techreport{sickn33-sickn33-fix-review-2026,
  author = {sickn33},
  title = {fix-review security audit report (audit version 4)},
  institution = {Skillstore},
  year = {2026},
  number = {4},
  url = {https://skillstore.io/skills/sickn33-fix-review/audits/4},
  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: "fix-review security audit report (audit version 4)"
version: "unspecified"
type: report
authors:
  - name: "sickn33"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/sickn33-fix-review/audits/4"
identifiers:
  - type: other
    value: "skillstore:sickn33-fix-review:audit:4"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Validate Remediation Pull Requests

Review a pull request that claims to resolve a security audit finding.

Check Regression Risk

Assess whether a fix changes nearby behavior or creates a new weakness.

Confirm Audit Closure

Prepare evidence that a finding was fixed before closing an audit item.

Try These Prompts

Review One Fix

Review this fix commit against the original audit finding. Explain whether the change resolves the issue and list any remaining concerns.

Check Root Cause

Compare the original vulnerability, affected data flow, and patch. Decide whether the root cause is fixed or only the symptom changed.

Assess New Risk

Analyze this remediation diff for new bugs, authorization gaps, input validation mistakes, and missing test coverage.

Audit Similar Patterns

After reviewing the fix, search the surrounding code for similar vulnerable patterns. Report whether additional remediation is needed.

Best Practices

Provide the original finding, fix diff, and relevant tests together.
Ask for root cause validation before accepting symptom-level changes.
Review nearby code paths for the same vulnerable pattern.

Avoid

Reviewing a patch without the original audit finding.
Accepting a fix only because a test was added.
Ignoring behavior changes outside the vulnerable function.

Frequently Asked Questions

Does this skill run security scanners?

No. It provides structured review guidance for evaluating fix commits and remediation evidence.

What inputs should I provide?

Provide the original finding, the fix diff, relevant files, and any tests that support the fix.

Can it confirm a finding is closed?

It can help assess closure, but final acceptance depends on reviewer judgment and available evidence.

Does it work with Claude Code?

Yes. The skill supports Claude, Codex, and Claude Code for guided remediation review.

Can it find similar vulnerable code?

Yes, it prompts the assistant to check nearby code for related patterns when context is available.

Is this only for security teams?

No. Developers and engineering leads can use it to review security fixes before merge or closure.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

Version notice

The author did not declare a version.

Repository

https://github.com/sickn33/antigravity-awesome-skills/tree/main/web-app/public/skills/fix-review

Ref

01171b582d636c013315c5e0d969c64f8d9cdff2

Maintenance freshness

7/18/2026

Usage

7 downloads · 102 views

File structure

📄 SKILL.md