Engineering Plugins for Claude Code

A collection of Claude Code plugins for common engineering workflows and use cases. Each plugin can be installed independently — pick only what you need.

Built by Donn Felker.

Contributions welcome! Found a way to improve a plugin or have a new one to add? Open a PR.

Run into a problem or have a question? Open an issue.

What are Plugins?

Plugins are packages of skills, commands, agents, and hooks that extend Claude Code with specialized capabilities. Each plugin in this marketplace focuses on a specific engineering workflow and can be installed independently.

Available Plugins

<!-- PLUGINS:START -->

<!-- PLUGINS:END -->

Moved to a new marketplace. triangulated-code-review, multi-llm-convergence, and the durable-spec-development bundle (now split into spec-development, dev-team, and pr-autopilot) have moved to the loop-skills marketplace. Install them from there:

/plugin marketplace add donnfelker/loop-skills
/plugin install spec-development@loop-skills
/plugin install dev-team@loop-skills
/plugin install pr-autopilot@loop-skills
/plugin install triangulated-code-review@loop-skills
/plugin install multi-llm-convergence@loop-skills

Installation

Option 1: CLI Install (Recommended)

Use npx skills to install skills directly:

# Install all plugins
npx skills add donnfelker/donnfelker-plugin-marketplace

# Install specific plugins
npx skills add donnfelker/donnfelker-plugin-marketplace --skill codebase-analyzer

# List available plugins
npx skills add donnfelker/donnfelker-plugin-marketplace --list

This automatically installs to your .claude/skills/ directory.

Option 2: Claude Code Plugin

Install via Claude Code's built-in plugin system:

# Add the marketplace
/plugin marketplace add donnfelker/donnfelker-plugin-marketplace

# Install a specific plugin
/plugin install codebase-analyzer@donnfelker-plugins

Option 3: Clone and Copy

Clone the repo and copy the plugins you want:

git clone https://github.com/donnfelker/donnfelker-plugin-marketplace.git
cp -r donnfelker-plugin-marketplace/plugins/codebase-analyzer .claude/plugins/

Option 4: Git Submodule

Add as a submodule for easy updates:

git submodule add https://github.com/donnfelker/donnfelker-plugin-marketplace.git .claude/donnfelker-plugins

Then reference plugins from .claude/donnfelker-plugins/plugins/.

Option 5: Fork and Customize

1. Fork this repository
2. Customize plugins for your specific needs
3. Clone your fork into your projects

Option 6: SkillKit (Multi-Agent)

Use SkillKit to install skills across multiple AI agents (Claude Code, Cursor, Copilot, etc.):

# Install all plugins
npx skillkit install donnfelker/donnfelker-plugin-marketplace

# Install specific plugins
npx skillkit install donnfelker/donnfelker-plugin-marketplace --skill codebase-analyzer

# List available plugins
npx skillkit install donnfelker/donnfelker-plugin-marketplace --list

Usage

Once installed, just use the skills naturally:

"Generate release notes since the last release"
→ Uses generate-release-notes plugin

"Analyze this codebase and write up the architecture"
→ Uses codebase-analyzer plugin

Or invoke skills directly:

/generate-release-notes

Plugin Categories

Git & Dev Workflow

• Coming soon

Documentation

• Coming soon

Code Review

• Coming soon

Technical Analysis

• Coming soon

Presentations & Media

• Coming soon

GitHub Workflow: PR Title Validation

This repository includes a GitHub Actions workflow (.github/workflows/pr-lint-title.yml) that validates PR titles against the Conventional Commits format using amannn/action-semantic-pull-request.

The workflow runs on every PR open, reopen, and title edit. It enforces that the PR title follows the type(scope): description format with a valid type and a lowercase description. If the title doesn't match, the check fails and the PR is blocked from merging.

This matters because GitHub's squash merge uses the PR title as the resulting commit message. By validating the title at the PR level, every merged commit on main is guaranteed to follow Conventional Commits — even if individual branch commits don't. This keeps git log clean and enables automated changelog generation, semantic versioning, and commit classification.

Enforced Rules

• Type must be one of: feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert
• Description must start with a lowercase letter
• Format: type(scope): [ticket] description

Example

feat(auth): tos-123 add login support

If a PR title fails validation, the error message includes the expected format so you can correct the title.

Contributing

Found a way to improve a plugin? Have a new one to suggest? PRs and issues welcome!

See CONTRIBUTING.md for guidelines.

License

MIT — use these however you want.