From devflow
Scans for security vulnerabilities in branch changes, full repo, or specific files. Supports interactive triage — fix, dismiss, create ticket, or defer each finding. Use this to perform security analysis before creating a PR/MR or on any part of the codebase.
npx claudepluginhub joshuarweaver/cascade-code-general-misc-4 --plugin codingthefuturewithai-claude-code-primitivesThis skill is limited to using the following tools:
I'll perform a comprehensive security analysis.
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
I'll perform a comprehensive security analysis.
Parse $ARGUMENTS for:
Load backend configuration from devflow-config.md to determine issue tracker for ticket creation.
If ISSUE_KEY provided: Scope is branch changes — find files modified since branching from the base branch.
If no ISSUE_KEY: Ask user what to scan:
Display the files that will be analyzed and their count.
Use the Task tool with subagent_type="security-scanner" to analyze the scoped files.
Provide the agent with:
The agent autonomously reads files, identifies vulnerabilities, and provides remediation guidance.
Display the security assessment summary:
If no findings: Skip to Next Steps.
Before triage:
.devflow/security/[ISSUE_KEY]-dismissed.json exists, load dismissed issuesFor each finding, present:
Ask user for each finding — one at a time:
Actions:
.devflow/security/[ISSUE_KEY]-dismissed.json with reason and date. Future reviews skip these automatically.Repeat for all findings.
After all findings triaged, show:
If fixes were applied, commit them referencing the issue key.
If dismissals were recorded, note the dismissed issues file path and how to review them with --show-dismissed.
If ISSUE_KEY was provided:
/devflow:build:complete-issue [ISSUE_KEY]If general scan: Review triage summary. Re-scan after manual fixes if needed.