Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
npx claudepluginhub j0hanz/claude-agent-dev-pluginAutonomous code execution agent. Executes tasks, refactors code, and applies improvements to any codebase you're pointed at. Use this agent when you need to: - Implement a specific feature or fix a bug in a codebase. - Refactor or clean up existing code for better maintainability. - Run diagnostic scripts or tests to identify issues. - Perform batch updates or automated changes across multiple files. <example> "Implement the retry logic in hooks/handlers/format.mjs and run the tests to confirm it passes." </example> *Note: This agent requires the `managed-agents-2026-04-01` beta header.*
Code debugging specialist. Diagnoses runtime failures, logic bugs, and quality inconveniences through systematic root-cause analysis so the main thread does not have to context-switch between reading code, logs, and tracing call chains. Use this agent when you need to: - Identify the root cause of a runtime failure or logic bug. - Analyze error logs and stack traces to trace back to the source of an issue. - Classify bugs by severity and category to prioritize fixes. - Propose code fixes as diffs or replacement blocks without applying them. <example> "Investigate the NullPointerException in the user authentication flow and explain the root cause with a proposed fix." </example>
Documentation maintenance agent. Audits, writes, and keeps all docs in sync with the codebase. Use this agent when you need to: - Create or update README files, API docs, or inline code comments. - Audit existing documentation for staleness, gaps, or inaccuracies. - Generate architecture decision records (ADRs) or changelog entries. - Write skill documentation, agent descriptions, or hook reference guides. - Synchronize docs after a refactor — ensuring names, paths, and examples are current. <example> "Update the README to reflect the new hook runner architecture and add a Mermaid diagram." </example> *Note: This agent requires the `managed-agents-2026-04-01` beta header.*
Research-focused agent for exploring codebases and documentation. Use this agent when you need to: - Explore a new codebase and understand its structure and dependencies. - Research documentation for libraries, frameworks, or external APIs. - Search for specific symbols, patterns, or file usages across a project. - Gather information before starting a complex task. <example> "Explore the hook handling logic and find all places where PreToolUse is emitted." </example> *Note: This agent requires the `managed-agents-2026-04-01` beta header.*
Create, audit, refactor, or trim AGENTS.md, CLAUDE.md, GEMINI.md, and onboarding guides. Trigger on 'agent docs', 'instructions', 'onboard me', 'understand this repo', 'setup AGENTS.md', 'this file is too long', 'trim CLAUDE.md', 'improve agent instructions', 'add conventions', 'update instructions file', or when the user shares an existing AGENTS.md/CLAUDE.md and asks to improve, review, or clean it up.
Use when a codebase has structural problems (circular deps, God modules, testability issues) or when designing new systems. Trigger on 'architecture review', 'where should this code live', 'too coupled', 'God class', 'design this system'.
Structured requirements discovery before implementation. Trigger on 'let's build', 'add a feature', 'we need a new', 'I want to implement', 'add X to', 'create a Y', ambiguous design, or unclear terminology — even when the user says 'just build it'. Proactively offer before any implementation begins. Prevents rework by catching problems early.
Mandatory quality gate before delivery. Trigger on 'code review', 'review this diff', 'any issues with this', 'check for bugs', 'quality review', 'ready to merge'. ALSO trigger automatically: (1) after verification-before-completion confirms tests pass, (2) before opening a PR/shipping the change, (3) on any non-trivial change that will be committed. Do not skip — correctness bugs and security issues discovered here are cheaper to fix than after merge.
Design, write, test agents and subagents. Trigger on 'build agent', 'create subagent', 'agent prompt', 'multi-agent', 'managed agent', 'agent not working', 'agent keeps triggering wrong thing'. Also: agent role selection, permission scoping, tool surface design, choosing between subagent/team/workflow/managed agent.
Hook handler unit tests — live feedback during hook development
Skill script tests — live feedback during skill development
Hook execution telemetry — surfaces errors and slow hooks in real time (PowerShell)
Executes bash commands
Hook triggers when Bash tool is used
Modifies files
Hook triggers on file write and edit operations
External network access
Connects to servers outside your machine
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Access thousands of AI prompts and skills directly in your AI coding assistant. Search prompts, discover skills, save your own, and improve prompts with AI.
Comprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.
Develop, test, build, and deploy Godot 4.x games with Claude Code. Includes GdUnit4 testing, web/desktop exports, CI/CD pipelines, and deployment to Vercel/GitHub Pages/itch.io.
Permanent coding companion for Claude Code — survives any update. MCP-based terminal pet with ASCII art, stats, reactions, and personality.
Comprehensive feature development workflow with specialized agents for codebase exploration, architecture design, and quality review
Reliable automation, in-depth debugging, and performance analysis in Chrome using Chrome DevTools and Puppeteer
Uses power tools
Uses Bash, Write, or Edit tools
Uses power tools
Uses Bash, Write, or Edit tools
Share bugs, ideas, or general feedback.
A Claude Code plugin for authoring and maintaining agents, skills, and hooks — structured workflows, managed subagents, and lifecycle hooks that guide Claude through the full agent development lifecycle.
Agent Dev Plugin extends Claude Code with 14 skills, 4 managed subagents, and 8 lifecycle hooks covering the complete agent development cycle. Skills activate automatically based on task context and can also be invoked manually; hooks fire on every session event to keep development disciplined; agents handle specialized tasks in scoped, isolated environments.
| Aspect | Detail |
|---|---|
| Status | Stable — v1.0.0 |
| Language | JavaScript (ESM) · Python |
| Runtime | Node.js ≥ 22 · Python ≥ 3.10 |
| Package manager | npm |
| License | MIT |
| Feature | Description |
|---|---|
| 14 auto-triggered skills | Activate on task context; invoke manually with /skill-name |
| 4 specialized subagents | Scoped tool access — executor, debugger, documenter, researcher |
| 8 lifecycle hooks | Fire on session events to enforce workflow discipline automatically |
| Marketplace install | One-command install from GitHub — no manual clone required |
[!TIP] Marketplace install is recommended — upgrades are handled automatically.
.claude/settings.json:{
"extraKnownMarketplaces": {
"claude-agent-dev": {
"source": {
"source": "github",
"repo": "j0hanz/claude-agent-dev-plugin"
}
}
}
}
claude plugin install claude-agent-dev@claude-agent-dev
git clone https://github.com/j0hanz/claude-agent-dev-plugin.git
claude --plugin-dir ./claude-agent-dev-plugin
| Requirement | Version / Notes |
|---|---|
| Node.js | ≥ 22 |
| Python | ≥ 3.10 |
| Claude Code | latest |
| Python packages | pip install pytest pyyaml jsonschema |
Skills are invoked automatically by Claude based on task context, or manually with /skill-name.