Claude Code instructions for pitimon/claude-cybersecurity-skill, covering claude.md, what this is, architecture, how it works at runtime and key files.
Use when asked to generate professional cybersecurity documents — IR playbooks, DFIR forensic reports, SOC L1–L3 triage runbooks, DevSecOps pipeline configs, threat models, compliance gap analyses, or executive cyber-risk reports. Covers 22 domains across AppSec / Cloud / OT / AI-ML / API / Identity / Web3, bilingual…
Instructions for pitimon/8-habit-ai-dev, covering claude.md, what this is, validation commands, the plugin/ mirror (edit → sync, always) and architecture.
Deep cross-verification reviewer — evaluates plans and code against all 8 habits. Use after completing a feature, before creating a PR, or when asked for a habit review.
Citation-integrity verification agent — validates cited URLs, checks file path existence, flags dead links in research briefs. Use during /research Deep mode or when evidence verification is needed. Read-only analysis. Does NOT verify semantic correctness of conclusions (e.g. "this dep is unused") — those require…
Generate AI-assisted development log from git history + Co-Authored-By trailers. Use for EU AI Act Article 11 (technical documentation) audit trail and AI transparency. Maps to H4 (Win-Win — honest disclosure) + H1 (Be Proactive — audit-ready).
Decompose feature into atomic tasks — 1 task per agent. Use AFTER /design and BEFORE /build-brief. Step 3 of 7-step workflow. Maps to H3 (First Things First).
Generate context-rich implementation brief before coding. Use AFTER /breakdown for each task. Step 4 of 7-step workflow. Maps to H5 (Seek First to Understand).
Assess your 8-habit maturity level via 5-7 questions and persist a profile to /.claude/habit-profile.md. Other skills read this profile to adapt their verbosity — Dependence (full guidance) → Independence (key checkpoints) → Interdependence (team focus) → Significance (minimal prompts). Maps to H8 (Find Your Voice …
Cross-artifact and incident/config consistency analyzer — runs 5 detection passes across persisted spec artifacts (PRD ↔ design ↔ tasks), or a lightweight symptom/evidence/root-cause/fix check for operational hotfixes that lack persisted specs. Use AFTER /requirements, /design, /breakdown have been run with --persist…
Run 17-question 8-Habit cross-verification checklist on a plan or implementation. Use AFTER planning and BEFORE committing to implementation. Maps to ALL 8 Habits.
Step-by-step deployment assistance with rollback planning. Use when deploying to staging or production. Step 6 of 7-step workflow. Maps to H1 (Be Proactive).
Produce architecture decisions — DB, auth, API, constraints. Use AFTER /requirements and BEFORE /breakdown. Step 2 of 7-step workflow. Maps to H8 (Find Your Voice).
Active bug investigation discipline — 6-phase methodology covering feedback-loop, reproduce, hypothesise, instrument, fix-with-regression-test, and cleanup-with-post-mortem. Use when investigating a hard bug or performance regression that doesn't have an obvious root cause. Triggers: "diagnose", "debug this"…
EU AI Act compliance — migrated to pitimon/claude-governance v3.1.0. This stub redirects to the canonical implementation. Maps to H1 (Be Proactive — prevent regulatory crisis) + H8 (Voice/Conscience).
Reshape engineer-to-engineer content for engineering-org leadership (VPs, directors, PMs, release managers) and shape it for the channel — JIRA comment, Slack post, async standup, email, or meeting talking-points. Use AFTER /post-mortem or any engineering writeup when the same information needs to flow up-the-org.…
Classify operational findings before action: Watch, Fix Candidate, Active Incident, Resolved, Handoff, Known Accepted Issue, False Positive, or Self-Resolved. Use when an infra/app/alert finding is not simply "fix" or "done", especially when recovered-but-recurring signals, Running-but-unhealthy workloads, ownership…