Claude Code Plugins

A collection of Claude Code plugins for enhanced development workflows with AI assistants.

Available Plugins

ai-delegation

Delegate tasks to external AI models and run autonomous maintenance loops.

• Type: Skill-based plugin
• Skills: /delegate-to-ai, /auto-maintain
• Purpose: Route tasks to Gemini, local Ollama, or other models via PAL MCP

codeql-resolver

Systematic CodeQL alert analysis and resolution for GitHub Actions workflows.

• Type: Command/Skill/Agent-based plugin
• Command: /resolve-codeql
• Purpose: Resolve CodeQL security alerts in GitHub Actions workflows

config-management

Sync AI tool permissions across repos and quickly add always-allow permissions.

• Type: Skill-based plugin
• Skills: /sync-permissions, /quick-add-permission
• Purpose: Manage Claude and Gemini permission configs across repositories

content-guards

Combined content validation and guard plugin.

• Type: Pre/PostToolUse hook
• Tools: Bash, Write, Edit
• Purpose: Token limits, markdown/README validation, webfetch guard, issue/PR rate limiting

git-guards

Combined git security and workflow protection via PreToolUse hooks.

• Type: PreToolUse hook
• Tools: Bash, Edit, Write, NotebookEdit
• Purpose: Blocks dangerous git/gh commands and file edits on main branch

git-workflows

Git main branch sync, repository refresh, and PR merge workflows.

• Type: Command/Skill-based plugin
• Skills: /sync-main, /refresh-repo, /rebase-pr, /troubleshoot-rebase, /troubleshoot-precommit, /troubleshoot-worktree
• Purpose: Maintain linear git history and keep branches in sync

github-workflows

PR finalization, squash-merge, review thread resolution, and issue shaping.

• Type: Command/Skill-based plugin
• Skills: /finalize-pr, /squash-merge-pr, /resolve-pr-threads, /shape-issues, /trigger-ai-reviews
• Purpose: GitHub PR/issue management workflows

infra-orchestration

Cross-repo infrastructure orchestration for Terraform and Ansible workflows.

• Type: Skill-based plugin
• Skills: /orchestrate-infra, /sync-inventory, /test-e2e
• Purpose: Coordinate infrastructure changes across multiple repositories

process-cleanup

Cleanup orphaned MCP server processes on session exit.

• Type: PostToolUse hook
• Purpose: Workaround for upstream MCP orphan-process bug (#1935)

Installation

From Marketplace

claude plugins add jacobpevans-cc-plugins/<plugin-name>

Available plugins:

• jacobpevans-cc-plugins/ai-delegation
• jacobpevans-cc-plugins/codeql-resolver
• jacobpevans-cc-plugins/config-management
• jacobpevans-cc-plugins/content-guards
• jacobpevans-cc-plugins/git-guards
• jacobpevans-cc-plugins/git-workflows
• jacobpevans-cc-plugins/github-workflows
• jacobpevans-cc-plugins/infra-orchestration
• jacobpevans-cc-plugins/process-cleanup

Local Development

Clone this repository and link plugins:

git clone https://github.com/JacobPEvans/claude-code-plugins.git
cd claude-code-plugins
claude plugins link ./ai-delegation
claude plugins link ./codeql-resolver
claude plugins link ./config-management
claude plugins link ./content-guards
claude plugins link ./git-guards
claude plugins link ./git-workflows
claude plugins link ./github-workflows
claude plugins link ./infra-orchestration
claude plugins link ./process-cleanup

Plugin Structure

Each plugin follows Claude Code official best practices. Most plugins use hook-based structure:

plugin-name/
├── .claude-plugin/
│   └── plugin.json       # Plugin metadata
├── hooks/
│   └── hooks.json        # Hook configuration
├── scripts/
│   └── hook-script.py    # Implementation
└── README.md             # Plugin documentation

Command/skill-based plugins use a different structure:

plugin-name/
├── .claude-plugin/
│   └── plugin.json       # Plugin metadata
├── commands/
│   └── command.md        # Command definition
├── skills/
│   └── skill-name/
│       └── SKILL.md      # Skill documentation
└── README.md             # Plugin documentation

Contributing

See individual plugin READMEs for specific details. General contribution guidelines:

1. Fork the repository
2. Create a feature branch: git checkout -b feature/your-feature
3. Follow conventional commits: feat(plugin): description
4. Sign your commits (GPG required)
5. Submit a pull request

Development

Requirements

• Claude Code CLI
• Python 3.10+ (for hook scripts)
• bats-core (for running tests)
• Tool-specific dependencies (see individual plugin READMEs)

Testing Plugins Locally

# Link a plugin for testing
claude plugins link ./plugin-name

# Verify it loaded
claude plugins list

# Test functionality
# (trigger the hook conditions for the specific plugin)

Running Tests

Run the shared test runner to execute all plugin tests:

# Run all tests
./scripts/run-tests.sh

# Run tests for a specific plugin
./scripts/run-tests.sh content-guards

# Alternative: run bats directly on a specific test file
bats tests/content-guards/**/*.bats

Git Hooks

Enable optional pre-push hooks that run tests before pushing:

# Enable git hooks
git config core.hooksPath .githooks

# Disable git hooks
git config --unset core.hooksPath

Repository Integration

Nix Flake Auto-Update

This repository automatically triggers Nix flake updates when changes are merged to main. This ensures downstream repositories (like nix-config) immediately pull in plugin updates instead of waiting for scheduled updates.

How It Works

1. Changes merged to main branch trigger .github/workflows/trigger-nix-update.yml
2. Workflow sends a repository_dispatch event to the nix repository
3. Nix repository's deps-update-flake.yml workflow updates the claude-code-plugins flake input
4. Automated PR created with the updated flake.lock

Organization Secret Required

The trigger workflow requires a GitHub Personal Access Token (PAT) stored as an organization secret:

Secret Name: GH_PAT_WORKFLOW_DISPATCH

Required Scopes:

• repo - Full control of private repositories
• workflow - Update GitHub Action workflows

Setup Instructions:

1. Generate PAT: GitHub.com → Settings → Developer settings → Personal access tokens → Tokens (classic)
2. Select required scopes: repo and workflow
3. Set expiration to 1 year
4. Copy the token
5. Add as organization secret: Organization Settings → Secrets and variables → Actions → New organization secret
6. Name: GH_PAT_WORKFLOW_DISPATCH
7. Paste token value
8. Select repository access (all repositories or specific repos)

Security Notes:

• Token has minimal scopes (no admin, no packages)
• Rotate token annually before expiration
• Never expose token in logs or workflow outputs
• Organization-level secret is accessible to all repos

Reusable Pattern

This pattern can be replicated to any JacobPEvans repository that's a flake input. Simply:

1. Copy .github/workflows/trigger-nix-update.yml to the target repository
2. Update the flake_input_name field to match the flake input name in nix/flake.nix
3. No changes needed to the nix repository workflow (uses generic event type)

License

Apache License 2.0 - See LICENSE for details.

Author

JacobPEvans

• GitHub: @JacobPEvans
• Email: 20714140+JacobPEvans@users.noreply.github.com