spectra-audit

Name: spectra-audit
Availability: InStock
Author: PsychQuant

Audit git diffs for dangerous defaults, type confusion, and silent failures.

33|8|Updated Jan 13, 2026

Search Tags:#security #audit #static-analysis #risk-management #code-review #dev-ops #secure-by-default

Ready to run

npx skills add https://github.com/PsychQuant/che-ical-mcp --skill spectra-audit-psychquant

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spectra-audit
Source: https://github.com/PsychQuant/che-ical-mcp/tree/main/.agents/skills/spectra-audit
Command: npx skills add https://github.com/PsychQuant/che-ical-mcp --skill spectra-audit-psychquant

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit changed code for security sharp edges — dangerous defaults, type confusion, and silent failures.

Core Features & Use Cases

Standalone Mode: full 3-agent parallel analysis on current git diff to surface security issues.
Discipline Mode: integrated checks during implementation via spectra apply.
Core framework and triad perspective: assessments from Scoundrel, Lazy Developer, and Confused Developer to surface risks.

Quick Start

Run spectra-audit to start an audit of your current code changes against security traps.

Frequently Asked Questions about spectra-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I audit git diff for security vulnerabilities in changed code?▼

You can audit git diff for security vulnerabilities by running a static analysis on the current code changes to surface dangerous defaults, type confusion, and silent failures. This process targets security sharp edges introduced in your latest commits.

What is static analysis for dangerous defaults and silent failures?▼

Static analysis for dangerous defaults and silent failures is an automated code review process that identifies insecure configurations and hidden error paths. It enforces secure-by-default principles by surfacing type confusion and silent failure risks before deployment.

Can I integrate security audits into my dev-ops implementation workflow?▼

Yes, you can integrate security audits into your dev-ops workflow using Discipline mode, which runs integrated checks during implementation. This enforces continuous risk management and secure-by-default practices directly within your code review process.

What is the best way to review code changes for type confusion risks?▼

The best way to review code changes for type confusion risks is using a triad assessment framework that evaluates code from Scoundrel, Lazy Developer, and Confused Developer perspectives. This multi-agent parallel analysis surfaces hidden security vulnerabilities.

Does this security audit work on the full git diff or only specific files?▼

The security audit operates on the current full git diff in Standalone mode, performing a 3-agent parallel analysis across all changed code. This ensures comprehensive risk management coverage for your entire code changeset.

When should I not use automated code review for security risks?▼

You should reconsider automated code review for security risks when your changeset is empty or when you need runtime dynamic analysis rather than static-analysis. The audit specifically targets static security sharp edges in changed code, not runtime behavior.