A collection of powerful extensions for Claude Code including autonomous agents, slash commands, global configurations, and GitHub Actions workflows.
Security Auditor (agents/security-auditor.md)
- Elite Application Security Engineer with 15+ years of simulated expertise
- Comprehensive vulnerability scanning (OWASP Top 10, CVE databases)
- Static Application Security Testing (SAST) and dependency analysis
- Generates structured security audit reports with remediation guidance
- Use for pre-release audits, dependency checks, and security reviews
Project Architect (agents/project-architect.md)
- Elite Software Architect that analyzes any project's tech stack
- Automatically detects languages, frameworks, build tools, testing infrastructure
- Generates custom Claude Code agents, skills, and commands tailored to the project
- Creates workflow-specific extensions (test-runner, build-manager, linter-helper, etc.)
- Updates existing documentation (CLAUDE.md, README.md) to document new tools
- Use when setting up Claude Code for a new project or after major tech stack changes
Repository Maintenance Agents (.claude/agents/)
- markdown-linter - Validates agent and command files for proper YAML frontmatter and structure
- doc-sync-manager - Synchronizes documentation across README.md and CLAUDE.md
- template-validator - Ensures templates follow Claude Code best practices
- release-manager - Manages versioning, changelog generation, and releases
Project Setup Command
/setup-project-tools- Automatically analyze project and generate tailored agents, skills, and commands
Security Audit Command
/security-audit- Perform comprehensive security audit of the project (invokes security-auditor agent)
Repository Maintenance Commands
/validate-agents- Validate all agent files for proper structure and syntax/validate-commands- Validate all command files for proper structure and syntax/sync-docs- Synchronize documentation after adding/modifying agents or commands/test-workflows- Validate GitHub Actions workflow syntax and best practices/new-agent- Scaffold a new agent file with proper template/new-command- Scaffold a new command file with proper template
Commit Workflow Commands
/commit-prepare- Review changes and draft commit messages following best practices/commit-do- Create commits with proper formatting and HEREDOC syntax
Both commit commands enforce strict commit message standards:
- Subject line: max 50 chars, imperative mood
- Body: wrapped at 72 chars, explains what and why
- Clean messages without AI attribution footers
Located in global/ directory - copy these to your ~/.claude/ directory:
global/CLAUDE.md
- Strict git workflow rules (no automatic commits/pushes)
- Commit message formatting standards
- Platform-specific command compatibility (macOS/Linux)
- Permission file management guidelines
global/settings.json
- Custom status line showing project, git branch, and model
- Always-thinking mode enabled
- Template for team-wide settings
Automated PR Reviews (.github/workflows/claude-code-review.yml)
- Runs on PR open/synchronize events
- Reviews code quality, security, performance, and test coverage
- Posts feedback as PR comments
@claude Mention Response (.github/workflows/claude.yml)
- Triggers when
@claudeis mentioned in issues or PRs - Responds to requests with full repository access
- Supports issue comments, PR reviews, and new issues
Located in stacks/ directory - copy these to your project's .claude/ directory:
Go (stacks/go/)
- Pre-configured hooks, agents, and commands for Go development
validate-go-toolchain.sh- Blocks builds when Go version mismatches compilervalidate-go-test.sh- Recommends race detection for test commandscode-quality-auditoragent - Comprehensive code quality scanning/code-qualityand/commit-preparecommands with quality integration
Swift/Xcode (stacks/swift/)
- Pre-configured hooks for Xcode project development
validate-xcodebuild.sh- Ensures xcodebuild commands use correct simulator (iPhone 17 Pro)- Prevents build failures from incorrect simulator targets
Kotlin/Android (stacks/kotlin/)
- Pre-configured agents and commands for Android/Kotlin development
android-quality-auditoragent - Comprehensive Android code quality scanning (SDK, Gradle, dependencies, lint, Compose)kotlin-refactoreragent - Kotlin refactoring and best practicescompose-developeragent - Jetpack Compose UI development/code-quality,/lint,/clean,/test-instrumentedcommands
Security Policy (SECURITY.md)
- Vulnerability disclosure via GitHub Security Advisories
- 48-hour response SLA for security reports
- Token rotation policy (90 days for OAuth tokens)
- Incident response procedures
Threat Model (.github/THREAT_MODEL.md)
- Attack scenarios (expression injection, prompt injection, supply chain)
- Trust boundaries and security assumptions
- Implemented controls (preventive, detective, corrective)
- Residual risks and user recommendations
Supply Chain Security (.github/SUPPLY_CHAIN_SECURITY.md)
- GitHub Actions dependency inventory with pinned SHAs
- Verification process for adding new dependencies
- Incident response for supply chain compromises
Copy agent files to your project's .claude/agents/ directory:
cp agents/security-auditor.md /path/to/your/project/.claude/agents/Then invoke in Claude Code:
# In Claude Code conversation
Please use the security-auditor agent to audit this codebaseCopy command files to your project's .claude/commands/ directory:
# Project setup command
cp commands/setup-project-tools.md /path/to/your/project/.claude/commands/
# Commit workflow commands
cp .claude/commands/commit-prepare.md /path/to/your/project/.claude/commands/
cp .claude/commands/commit-do.md /path/to/your/project/.claude/commands/Then use in Claude Code:
/setup-project-tools
/commit-prepare
/commit-doCopy global files to your ~/.claude/ directory:
# Create directory if it doesn't exist
mkdir -p ~/.claude
# Copy global configuration
cp global/CLAUDE.md ~/.claude/
cp global/settings.json ~/.claude/These will apply to all your Claude Code sessions across all projects.
Copy stack-specific tools to your project:
# For Go projects
cp stacks/go/settings.json /path/to/your/project/.claude/
mkdir -p /path/to/your/project/.claude/hooks
cp stacks/go/hooks/*.sh /path/to/your/project/.claude/hooks/
chmod +x /path/to/your/project/.claude/hooks/*.sh
# Optional: Copy agents and commands
cp -r stacks/go/agents /path/to/your/project/.claude/
cp -r stacks/go/commands /path/to/your/project/.claude/
# For Swift/Xcode projects
cp stacks/swift/settings.json /path/to/your/project/.claude/
mkdir -p /path/to/your/project/.claude/hooks
cp stacks/swift/hooks/validate-xcodebuild.sh /path/to/your/project/.claude/hooks/
chmod +x /path/to/your/project/.claude/hooks/validate-xcodebuild.sh
# For Kotlin/Android projects
cp -r stacks/kotlin/agents /path/to/your/project/.claude/
cp -r stacks/kotlin/commands /path/to/your/project/.claude/-
Generate Claude Code OAuth Token
- Visit Claude Code settings
- Generate a new OAuth token for GitHub Actions
-
Add Secret to Repository
- Go to your repository Settings > Secrets and variables > Actions
- Add new secret:
CLAUDE_CODE_OAUTH_TOKEN - Paste your OAuth token
-
Copy Workflow Files
mkdir -p .github/workflows cp .github/workflows/claude-code-review.yml .github/workflows/ cp .github/workflows/claude.yml .github/workflows/
-
Customize as Needed
- Edit
claude_argsto restrict or expand allowed tools - Modify triggers and filters for your workflow
- Adjust review prompts and criteria
- Edit
Security Note: These workflows include security hardening (pinned actions, tool restrictions, trusted user checks). Before deploying, review SECURITY.md for token rotation requirements and best practices.
# In Claude Code - Option 1: Use slash command
/setup-project-tools
# Option 2: Invoke agent directly
Use the project-architect agent to analyze this project and generate
tailored Claude Code extensions for my tech stack.The agent will:
- Analyze your project (languages, frameworks, build tools, testing, etc.)
- Generate custom agents in
.claude/agents/(e.g., test-runner, build-manager) - Generate slash commands in
.claude/commands/(e.g., /test, /build, /lint) - Create skills in
.claude/skills/if needed - Update existing documentation (CLAUDE.md, README.md, etc.) with new tools
- Provide quick start guide for using the generated extensions
# In Claude Code
Use the security-auditor agent to perform a comprehensive security audit
of this codebase, focusing on authentication and API endpoints.The agent will generate multiple markdown reports:
security-audit-application-code.mdsecurity-audit-dependencies.mdsecurity-audit-authentication.mdsecurity-audit-api.mdsecurity-audit-summary.md
# Step 1: Review changes and prepare message
/commit-prepare
# Step 2: Create the commit
/commit-doSimply open a PR and the security-auditor will automatically:
- Analyze the changes
- Check for bugs, security issues, and code quality
- Post a review comment with findings
In any issue or PR comment:
@claude can you add unit tests for the new authentication module?
Claude will respond and complete the task with full repository access.
.
βββ agents/ # Autonomous agent definitions
β βββ security-auditor.md # Security vulnerability scanning
β βββ project-architect.md # Project analysis & tool generation
βββ .claude/
β βββ agents/ # Repository-specific agents
β β βββ markdown-linter.md # Validate agent/command files
β β βββ doc-sync-manager.md # Synchronize documentation
β β βββ template-validator.md # Validate template quality
β β βββ release-manager.md # Manage releases and versioning
β βββ commands/ # Repository-specific slash commands
β βββ commit-prepare.md # Review changes
β βββ commit-do.md # Create commits
β βββ security-audit.md # Security audit command
β βββ validate-agents.md # Validate agent files
β βββ validate-commands.md # Validate command files
β βββ sync-docs.md # Update documentation
β βββ test-workflows.md # Validate workflows
β βββ new-agent.md # Scaffold new agent
β βββ new-command.md # Scaffold new command
βββ commands/ # Template commands for copying to projects
β βββ setup-project-tools.md
β βββ no-ticket/ # Alternative command structures
βββ stacks/ # Stack-specific configurations
β βββ go/ # Go project tools
β β βββ settings.json # Hook configuration for Go commands
β β βββ hooks/
β β β βββ validate-go-toolchain.sh # Toolchain version validation
β β β βββ validate-go-test.sh # Test command recommendations
β β βββ agents/
β β β βββ code-quality-auditor.md # Code quality scanning agent
β β βββ commands/
β β βββ code-quality.md # Run quality checks
β β βββ commit-prepare.md # Commit with quality integration
β βββ swift/ # Swift/Xcode project tools
β β βββ settings.json # Hook configuration for xcodebuild
β β βββ hooks/
β β βββ validate-xcodebuild.sh # Simulator validation hook
β βββ kotlin/ # Kotlin/Android project tools
β βββ agents/
β β βββ android-quality-auditor.md # Android code quality auditor
β β βββ kotlin-refactorer.md # Kotlin refactoring agent
β β βββ compose-developer.md # Jetpack Compose development
β βββ commands/
β βββ code-quality.md # Run quality checks
β βββ lint.md # Run Android Lint
β βββ clean.md # Clean build artifacts
β βββ test-instrumented.md # Run instrumented tests
βββ global/ # User-level configuration templates
β βββ CLAUDE.md
β βββ settings.json
βββ .github/
β βββ workflows/ # GitHub Actions workflows
β β βββ claude.yml
β β βββ claude-code-review.yml
β βββ THREAT_MODEL.md # Security threat model
β βββ SUPPLY_CHAIN_SECURITY.md # Supply chain security policy
βββ SECURITY.md # Vulnerability disclosure policy
This repository has no runtime dependencies. It consists entirely of:
- Markdown documentation and agent definition files
- YAML configuration files for GitHub Actions
- JSON configuration files
If dependencies are added in the future, they must:
- Use lockfiles (package-lock.json, go.sum, etc.)
- Be scanned for vulnerabilities with Dependabot
- Follow semantic versioning
- Have versions pinned in production
Feel free to add your own:
- Agents - Create specialized agents for different domains (testing, refactoring, documentation, etc.)
- Commands - Build workflow-specific slash commands
- Workflows - Share GitHub Actions configurations for different use cases
MIT License - see LICENSE file for details.