Audit git diffs for security sharp edges and API misuse.
npx skills add https://github.com/ycs77/gh-aw-todo-app --skill spectra-audit-ycs77
Please help me install this Agent Skill. Skill: spectra-audit Source: https://github.com/ycs77/gh-aw-todo-app/tree/main/.claude/skills/spectra-audit Command: npx skills add https://github.com/ycs77/gh-aw-todo-app --skill spectra-audit-ycs77
Spectra Audit helps developers and reviewers find security "sharp edges" introduced by recent changes, such as dangerous defaults, type confusion, silent failures, and insecure API surfaces that rely on developer vigilance.
Run the spectra-audit skill against the current git diff to list security issues, classify severity, and propose fixes.
High-intent search queries and answers about installing and using this skill.
Static analysis of API security in changed code detects dangerous defaults, type confusion, silent failures, and insecure API surfaces that rely on developer vigilance, targeting git diffs to surface regressions and risky public API changes.
To audit changed code for security issues, run the spectra-audit skill against your current git diff to list detected issues, classify severity from Critical to Low, and propose or apply safe fixes to your codebase.
Yes, you need access to the repository git diff and the spectra CLI when using the audit skill standalone to analyze configuration changes, API signatures, and cryptographic usage for security pitfalls.
Yes, parallel adversary analysis runs three simultaneous perspectives—Scoundrel, Lazy Developer, and Confused Developer—on changed code to reveal different misuse patterns, attack vectors, and dangerous defaults introduced by recent changes.
Risk classification for security findings works by merging results from parallel analysis and assigning severity levels—Critical, High, Medium, or Low—to consolidated findings, then suggesting or applying fixes where safe.
Security sharp edges to look for in configuration changes include dangerous defaults, type confusion, silent failures, and insecure API surfaces that rely on developer vigilance, targeting changed lines to surface regressions.
kaochenlongAudit git diffs for security sharp edges using the spectra CLI.
cashwuAudit changed code for security vulnerabilities using a multi-agent approach.
Avi977Detect timing leaks in cryptographic implementations using constant-time analysis.
matteocervelliScan codebases for secrets, vulnerable dependencies, and insecure patterns.
