secdevai-fix
/secdevai-fix
Apply suggested security fixes from a prior code review. Use when the user wants to remediate security findings with before/after code diffs, severity filtering, and explicit approval before modifying code.
- Author
- redhatproductsecurity ↗
- Repository
- prodsec-skills ↗
- Licence
- Apache-2.0
- Last repository change
- 15.07.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 2
No signals detected. Repository changed on 15.07.2026, without references to retired models or APIs.
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
Apply suggested security fixes from a prior code review. Use when the user wants to remediate security findings with before/after code diffs, severity filtering, and explicit approval before modifying code.
Original author description
Apply suggested security fixes from a prior code review. Use when the user wants to remediate security findings with before/after code diffs, severity filtering, and explicit approval before modifying code.
How it works
- When to Use This Skill
- Workflow
- Important Rules
SKILL.md preview
---
name: secdevai-fix
description: >
Apply suggested security fixes from a prior code review. Use when the user
wants to remediate security findings with before/after code diffs, severity
filtering, and explicit approval before modifying code.
category: "security_auditing"
subcategory: "audit-workflow"
---
# Security Fix Application
Applies security fixes identified by a prior code review. Always shows a diff
preview and requires explicit user approval before modifying any file.
## When to Use This Skill
- Applying fixes for findings from a prior `secdevai-review` or equivalent
security review
- Applying a filtered subset of fixes (e.g., only critical severity findings)
- Previewing proposed code changes before deciding whether to apply them
## Workflow
### Step 1: Verify Prerequisites
Confirm that a prior security review has been run and findings are available.
If no prior review exists, inform the user and suggest running a security
review first.
### Step 2: Apply Severity Filter (optional)
If the user specifies a severity level (critical, high, medium, low), limit
fixes to findings at that level or above. If no filter is specified, present
all available fixes.
### Step 3: Present Fixes
For each fix, show:
- **Finding**: Description and location (file and line number)
- **Severity**: The severity of the finding being fixed
- **OWASP / CWE reference**: Category and ID
- **Before**: The vulnerable code
- **After**: The fixed code
- **Security impact**: What the fix prevents
Example:
```markdown
## Fix #1 (Critical)
**Finding**: SQL Injection in `app.py:42`
**OWASP Category**: [A03: Injection](https://owasp.org/Top10/A03_2021-Injection/) ([CWE-89](https://cwe.mitre.org/data/definitions/89.html))
**Before**:
query = f"SELECT * FROM users WHERE id = {user_id}"
**After**:
cursor.execute("SELECT * FROM users WHERE id = %s", (user_id,))
**Security impact**: Eliminates SQL injection by using a parameterized query.
The database driver handles escaping, preventing attacker-controlled input from
modifying query structure.
```
### Step 4: Require Explicit Approval
Before applying any changes:
- Show all proposed diffs
- Ask the user to confirm which fixes to apply
- Never modify code without explicit approval
- Never apply fixes in bulk without showing each change first
### Step 5: Apply Approved Fixes
After the user approves:
- Apply the approved code changes exactly as shown in the preview
- Report which fixes were applied and which were skipped
- If a fix cannot be applied cleanly (e.g., the file has changed), report the
conflict and leave the file unchanged
## Important Rules
- **Always preview before modifying**: Show the exact diff before touching any
file.
- **Never apply without approval**: Require explicit confirmation, even when the
user says "apply all".
- **Respect scope**: Only fix findings from the current review session unless the
user explicitly provides findings from elsewhere.
- **Report outcomes**: After applying, list what changed and what was skipped,
with reasons.
Versions
The database has no other skills named secdevai-fix.
Database snapshot: 13.11.2026 · package version 966e96bc324a (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
- 90security-cleanup
Applies fixes for security findings produced by /security-review. Use when the user wants to fix security issues found by /security-review or when they ask to clean up, remediate, or apply fixes for security findings. - 100secdevai-review
Use when performing security code review of source files, git commits, or entire codebases against OWASP Top 10 (2021), CWE/SANS Top 25, and OWASP WSTG v4.2 patterns; applicable to any language or framework. - 90team-security-review
Use for running the Team security review phase only on explicit request. Never infer from a plain security review request. Reviews and fixes the branch. - 100threat-patch
Remediate security findings by producing minimal, surgical code patches. Triggers on 'patch security findings', 'fix vulnerabilities', 'remediate findings', 'threat patch', or when the user provides a findings.json (from threat-model), a Codex security findings CSV, a… - 90podori-egov
Use when eGovFrame code needs security review or fixes. Apply version-specific security rules, code cases, and regression checks. - 90remediate
Propose fixes for the security audit findings of a synthesized CDK app, each with a concrete change and a way to verify it. Nothing is applied. Use after an audit when the user asks how to fix the findings.