claude-code-agents

agent
Security Audit
Warn
Health Warn
  • License — License: MIT
  • Description — Repository has a description
  • Active repo — Last push 0 days ago
  • Low visibility — Only 5 GitHub stars
Code Pass
  • Code scan — Scanned 12 files during light audit, no dangerous patterns found
Permissions Pass
  • Permissions — No dangerous permissions requested

No AI report is available for this listing yet.

SUMMARY

Self-healing AI agent framework for Claude Code: 13 specialized SDLC/SSDLC agents, 26 skills, 13 slash commands, 9 hooks, launchd watchdog daemon, observability dashboard. Auto-activating, drift-reconciling, snapshot-protected.

README.md

Claude Agents - AI-Powered SDLC Agent System

License: MIT
Version
Claude Code
Agents
Skills
MCP

13 auto-activating AI agents for every phase of software development. Just describe what you want to build — the right specialists engage automatically.

Works with Claude Code (Anthropic's CLI). No plugins, no configuration, no commands to memorize.

Requirements: macOS or Linux with bash and git; jq and npx are optional (used for the statusline and MCP examples). See INSTALL.md for updating, cross-machine migration, and the autonomous self-heal setup.


30-Second Setup

git clone https://github.com/pfangueiro/claude-code-agents.git
cd claude-code-agents
./install.sh

Installs once, user-global to ~/.claude. Now every project on your machine has the agents — open any project with Claude Code and talk naturally:

"Build a REST API with JWT authentication"
"This query is running slow"
"Check for security vulnerabilities"
"Deploy to production"

Agents activate automatically based on your words.


What You Get

Component Count What It Does
Agents 13 Auto-activating SDLC specialists (planning through production)
Skills 28 Modular knowledge packages (git, Docker, CI/CD, K8s, SRE, IaC, observability, experiment-loop, scheduled-tasks, worktree-workflow, remote-triggers, context-escalation, diverge, etc.)
Slash Commands 13 /commit-pr, /review-pr, /security-scan, /compact, /new-feature, /create-jira, /build-fix, /tdd, /quality-gate, /checkpoint, /save-session, /resume-session, /optimize
MCP Servers 4 context7, sequential-thinking, playwright, github
Rules 6 Auto-enforced security, code quality, fix quality, verification, framework integrity, and anti-anchoring standards
Hooks 10 Agent tracking, session lifecycle, permission auditing, file protection, auto-lint, debug detection, pre-compact snapshots, notifications

Available Agents

Agent Activates On Does What Model
architecture-planner "design", "architecture", "system" System design, API specs, ADRs Sonnet
code-quality "review", "refactor", "quality" Code review, best practices Sonnet
security-auditor "security", "auth", "vulnerability" OWASP scanning, security fixes Opus
test-automation "test", "coverage", "TDD" Test generation, coverage analysis Sonnet
performance-optimizer "slow", "optimize", "bottleneck" Profiling, caching, optimization Sonnet
devops-automation "deploy", "CI/CD", "Docker" Deployment, containerization Sonnet
documentation-maintainer "document", "README", "guide" Docs, API specs Haiku
database-architect "database", "SQL", "schema" Query optimization, migrations Sonnet
frontend-specialist "UI", "React", "frontend" Components, responsive design Sonnet
api-backend "API", "backend", "endpoint" REST/GraphQL, business logic Sonnet
incident-commander "CRITICAL", "outage", "emergency" Rapid response, root cause Opus
sre-specialist "SLO", "reliability", "on-call", "runbook" SRE, SLOs, capacity, chaos eng Sonnet
meta-agent "create an agent for..." Generates new custom agents Opus

Cost optimization: Haiku for docs (95% cheaper), Sonnet for dev work, Opus for security/emergencies.


How Agents Collaborate

Agents hand off work automatically. Example: "Build a user registration system"

graph LR
    A[architecture-planner] --> B[frontend-specialist]
    A --> C[api-backend]
    C --> D[database-architect]
    B --> E[test-automation]
    C --> E
    E --> F[code-quality]
    F --> G[security-auditor]
    G --> H[devops-automation]

See .claude/lib/agent-coordination.md for the formal handoff protocol.


Installation

One install, user-global. Claude Code natively loads ~/.claude/{agents,skills,commands,rules}, so a single install makes the agents available in every project on your machine — no per-project setup.

Command What It Does
./install.sh Install everything to ~/.claude: agents, skills, commands, rules, hooks, MCP, global config
./install.sh --update Reconcile an existing install to the latest version
./install.sh --upgrade Migrate from an old per-project install: reconcile, confirm + tear down old copies, then self-verify (details)
./install.sh --help Show all options

Verify Installation

./validate.sh
# All validations passed! (full + --quick modes)

Installed components live under ~/.claude/ — verify with ls ~/.claude/agents ~/.claude/skills ~/.claude/commands ~/.claude/rules.


Slash Commands

Project Workflow

Command Usage What It Does
/commit-pr /commit-pr [message] Stage, commit, push, create PR, update JIRA
/review-pr /review-pr 123 Code quality + security + testing review
/security-scan /security-scan [path] OWASP scanning, secrets detection, dependency audit
/compact /compact [note] Write HANDOFF.md with session context, then compact conversation
/new-feature /new-feature PROJ-123 desc Create feature branch from latest main
/create-jira /create-jira epic Title Create JIRA issue and assign to you

Developer Workflow (new in v2.5.0)

Command Usage What It Does
/build-fix /build-fix [path] Auto-detect build system, fix errors one at a time with regression guard
/tdd /tdd <feature> Enforce RED-GREEN-REFACTOR: failing test → implement → refactor
/quality-gate /quality-gate [path] [--fix] Pre-commit validation: formatter + linter + type checker + tests
/checkpoint /checkpoint <name> Named save points via git branches for complex multi-step work
/save-session /save-session [id] Save structured session state with mandatory "What Did NOT Work" section
/resume-session /resume-session [id] Resume from a saved session with context briefing and file state verification
/optimize /optimize <metric> [--iterations N] Autonomous metric-driven improvement loop: measure → improve → keep/revert

Skills System

Skills provide domain knowledge that agents apply. 28 included:

Skill What It Provides
git-workflow Branching strategies, conventional commits, PR workflows
code-review-checklist 10-category review framework, security checklist
deployment-runbook Blue-green deployment, rollback procedures, health checks
api-guidelines REST/GraphQL patterns, input validation, error handling
api-contract-testing OpenAPI validation, PACT testing, mock servers
ui-guidelines React/Next.js patterns, Ant Design, responsive design
ci-cd-templates GitHub Actions, GitLab CI, deployment strategies
docker-deployment Multi-stage builds, Docker Compose, security
execute Orchestrated task engine: decompose goals, plan dependencies, parallel execution
investigate 8-phase root cause analysis: observe, reproduce, trace, hypothesize, prove, fix, prevent
library-docs MCP-powered: fetch docs for React, Next.js, Vue, etc.
deep-analysis MCP-powered: structured reasoning with branching and revision (rewritten)
diverge Divergent ideation: isolated parallel sub-agents + critic pass; the divergent complement to deep-analysis
deep-read 6-phase codebase reading engine: scope, map, trace, deep read, connect, report
handoff Session continuity — write HANDOFF.md for cross-session context
context-escalation Five-level context-pressure policy: truncate → drop-reads → fork-subagent → /compact → handoff
security-scan Auto-activating security scanner (secrets, OWASP, dependencies, file permissions)
kubernetes-ops K8s manifests, Helm, Karpenter, GitOps (ArgoCD/Flux), network policies, troubleshooting
observability-stack OpenTelemetry, Prometheus/Grafana, RED/USE metrics, SLI/SLO monitoring, alerting
sre-runbooks On-call handbook, postmortem templates, SLO/error budgets, chaos engineering, capacity planning
infrastructure-as-code Terraform/CDK/Pulumi patterns, IaC testing pyramid, CI/CD for infra, state management
experiment-loop Autonomous experimentation pattern: modify → measure → keep/discard (autoresearch-inspired)
scheduled-tasks CronCreate/CronDelete/CronList for recurring prompts, polling, reminders
worktree-workflow Git worktree isolation for parallel development, experiments, risky refactors
remote-triggers RemoteTrigger API for cross-session automation, scheduled agents
browser-testing E2E testing with Playwright MCP — visual regression, responsive design, codegen
multi-agent-orchestration Coordinator pattern, teams, background agents, worker restrictions, SendMessage
skill-creator Create your own custom skills

Create Your Own Skill

python3 .claude/skills/skill-creator/scripts/init_skill.py my-skill --path .claude/skills

MCP Integration

4 Model Context Protocol servers, provided as an example config (.mcp.json.example) — install does not register them; add the ones you want to Claude Code with the commands below:

Server What It Does
context7 Fetch documentation for 100+ libraries on-demand
sequential-thinking Deep structured reasoning (31,999 thinking tokens)
playwright Browser automation and E2E testing
github PR/issue management via GitHub API

Manual MCP Setup

claude mcp add context7 -- npx @upstash/context7-mcp@latest
claude mcp add sequential-thinking-server -- npx @modelcontextprotocol/server-sequential-thinking
claude mcp add playwright -- npx @executeautomation/playwright-mcp-server
claude mcp add github -- npx -y @modelcontextprotocol/server-github

Auto-Enforced Rules

Six rule files in ~/.claude/rules/ are automatically loaded by Claude Code in every session:

  • security.md — No secrets in commits, parameterized queries, input validation, security headers, least privilege
  • code-quality.md — No dead code, single responsibility, early returns, explicit error handling, descriptive naming
  • fix-quality.md — Root cause analysis before fixing, never suppress errors, minimal changes, test-driven fixing
  • verification.md — Verify after every implementation, run tests, build to catch errors, test-driven bug fixes
  • framework-integrity.md — Hooks must enforce invariants, state reconciles automatically, snapshots have documented restore paths
  • anti-anchoring.md — Name the obvious pick + a non-obvious alternative + a trap on open-ended judgment calls; escalate consequential open decisions to /diverge

Hooks

10 hook events across 9 command hooks, installed globally to ~/.claude/hooks/:

Hook Event What It Does
session-start-healthcheck.sh SessionStart Fast-path framework drift check (<2s); forks install.sh --update on drift
file-protection.sh PreToolUse Blocks edits to sensitive files (.env, *.key, *.pem, secrets/)
post-edit-lint.sh PostToolUse Auto-lints TS/JS after Write/Edit, warns on debug statements
notify.sh Notification Desktop alert when Claude needs attention
agent-tracker.sh SubagentStart/Stop Real-time agent lifecycle tracking to analytics
session-end.sh SessionEnd Logs session completion for observability
smart-guard.sh PermissionRequest Auto-approves safe reads, audits dangerous operations
pre-compact.sh PreCompact Auto-saves session snapshot before context compaction
post-compact.sh PostCompact Verifies session snapshot was saved after compaction

Phase 2 reference configs (opt-in, not enabled by default):

  • smart-file-guard.json — prompt hook: LLM-based file protection
  • pre-commit-review.json — agent hook: automated code review before commit

Architecture

Installed once, user-global under ~/.claude/ — Claude Code loads it in every project:

~/.claude/
├── agents/          # 13 auto-activating SDLC agents
├── commands/        # 13 slash commands
├── skills/          # 28 modular knowledge packages
├── rules/           # 6 auto-enforced rule sets
├── lib/             # Templates, patterns, coordination protocol
├── hooks/           # 9 command hooks + 2 reference configs
├── daemon/          # launchd watchdog (hourly validate + snapshots)
├── analytics/       # Observability dashboard + ingested session logs
├── statusline.sh    # Rich status bar — ends line 1 with a framework-status glyph (✓ healthy / ⟳ self-healing / ⚠ stalled-or-degraded)
└── settings.json    # 10 hook events, permissions, model config

See EXTENSIBILITY.md for the complete guide on Skills, MCP, Slash Commands, and Subagents.


Usage Examples

Building a feature:

You: "Build a shopping cart with Stripe integration"
  → architecture-planner designs the system
  → api-backend implements payment logic
  → database-architect creates order schema
  → security-auditor validates payment security
  → test-automation generates tests
  → documentation-maintainer documents the API

Performance issue:

You: "The product search is running really slow"
  → performance-optimizer profiles the code
  → database-architect optimizes queries
  → code-quality suggests improvements

Production emergency:

You: "CRITICAL: Production API is returning 500 errors!"
  → incident-commander takes charge (Opus)
  → security-auditor checks for breaches
  → devops-automation prepares rollback

Observability Dashboard

Built-in analytics dashboard that reads Claude Code's native JSONL session logs — zero cloud dependencies, Python stdlib only, single SQLite database.

# Quick start (after install)
claude-obs

# Or run manually
python3 ~/.claude/analytics/collector.py    # Ingest JSONL → SQLite
python3 ~/.claude/analytics/server.py --open # Serve dashboard at localhost:3141

Dashboard panels:

  • Summary cards — total cost, projects, sessions, agent activations, input/output tokens
  • Daily cost & sessions — dual-axis bar+line chart with configurable time ranges (7d/14d/30d/All)
  • Cost by project — horizontal bar chart ranking projects by spend
  • Agent activations — which agents are used most and across how many projects
  • Model distribution — doughnut chart showing Opus/Sonnet/Haiku cost split
  • Top projects by tokens — token consumption per project
  • Sessions table — recent sessions with project, duration, cost, model, and agents used

Architecture:

  • Data source: ~/.claude/projects/**/*.jsonl (Claude Code writes these automatically)
  • Collector (collector.py): incremental JSONL scanner with per-file watermarks, per-model cost estimation (Opus/Sonnet/Haiku pricing)
  • Storage: SQLite with WAL mode at ~/.claude/analytics/claude-obs.db
  • Server (server.py): 6 JSON API endpoints + static file server on localhost:3141
  • Dashboard (dashboard.html): single-file dark-themed UI with Chart.js

CLI options:

python3 collector.py --full          # Re-ingest everything (ignore watermarks)
python3 collector.py --db /path/to.db # Custom database path
python3 server.py --port 8080        # Custom port
python3 server.py --open             # Auto-open browser

Installed automatically by ./install.sh. Data stays entirely local.


Contributing

  1. Fork the repository
  2. Create your feature branch (git checkout -b feature/my-feature)
  3. Run ./validate.sh to verify everything passes
  4. Commit your changes (git commit -m 'feat: add my feature')
  5. Push and open a Pull Request

Roadmap

  • VS Code extension
  • Observability dashboard
  • Lifecycle hooks (agent tracking, permission auditing, session lifecycle)
  • Additional specialized agents
  • Multi-language support
  • Team collaboration features
  • Custom agent marketplace

License

MIT License - see LICENSE for details.

Support


No configuration. No commands. Just describe what you need.

Built by Pedro Fangueiro with Claude

Reviews (0)

No results found