Sole mutator role — applies and verifies code, test, doc, and infra changes. Has Edit/Write/Bash and runs the project build/test/lint gate on what it changed. Use for implement, fix, refactor, or apply tasks. Not for read-only review (reviewer) or risk advice (advisor).
Read-only adversarial evaluator — reviews, audits, locates, or plans. Inspects with Read/Grep/Glob and does not modify code, run builds, or execute commands. Use for code review, security audit, locating code, or planning. Not for applying changes (engineer) or strategic risk verdicts (advisor).
Create normal git commits with logical grouping. Use when committing, saving changes, creating commits, or grouping work into commits. NOT for amending, rebasing, force-pushing, or rewriting history.
Create or update human-facing docs, agent-facing instructions, architecture docs, API docs, README content, and useful code comments from implementation facts. Use when docs are stale, missing, or must reflect code changes. NOT for code-quality review, prompt scoring, speculative docs, or ADRs unless explicitly requested.
Fix code defects with a reproducible feedback loop, root-cause diagnosis, minimal patch, regression test, and clean verification. Use when debugging, diagnosing, or resolving lint/test/build failures. NOT for behavior-preserving refactors (use refactoring-code), test-suite cleanup without a production bug (use improving-tests), or code review findings without fixes (use reviewing-code).
Improve test design, speed, and coverage with behavior-focused tests, useful seams, characterization tests, TDD, and test refactoring. Use when improving tests, optimizing slow suites, adding coverage, refactoring brittle tests, removing test waste, or working test-first. NOT for fixing production bugs (use fixing-code), production-code refactors (use refactoring-code), or reviewing non-test code quality (use reviewing-code).
Batch behavior-preserving refactors for multi-file, repeated-pattern, large-file, rename, move, extract, split, or restructure work. Use for "refactor across files", "batch rename", "update pattern everywhere", large files (500+ lines), or 5+ coordinated edits in one file. NOT for single targeted edits, behavior changes or bug fixes (use fixing-code), test-only refactors (use improving-tests), code review (use reviewing-code), or architecture redesign (use architecture-design/review).
Modifies files
Hook triggers on file write and edit operations
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Portable skills, agents, hooks, and Pi-native extensions for Claude Code, Codex CLI, GitHub Copilot, Cursor, Grok, and Pi. Gemini is retired.
Requires Agent Bundler with build, check, and package, plus support for
per-agent sidecars, declared hook environments, Pi-native assets, and Codex
project-agent profiles. Verify packaging support:
agbun package --help
Build and check the complete generated tree:
make build
make check
make build is a direct agbun build --root . invocation. make check runs
the non-mutating agbun check --root . drift gate. Agent Bundler replaces the
configured dist/ output tree during builds, so do not edit generated files.
agentbundle.json # Agent Bundler manifest
src/
├── skills/<name>/SKILL.md # canonical YAML-frontmatter skills
│ └── .agentbundler/targets/*.json # optional target overlays
├── agents/<name>.md # canonical agent assets
├── .agentbundler/packages/*.json # package membership and metadata
├── hooks/<name>/ # typed Agent Bundler hooks
└── plugins/pi/<asset>/ # declarative Pi-native extension tree
└── extensions/ # Pi-native tools and compatibility runner
dist/<target>/<package>/ # generated Agent Bundler package roots
.claude-plugin/marketplace.json # repository-root compatibility wrapper
.agents/plugins/marketplace.json # repository-root compatibility wrapper
.codex/agents/*.toml # fixed-path Codex project-agent profiles
.github/plugin/marketplace.json # repository-root compatibility wrapper
.cursor-plugin/marketplace.json # repository-root compatibility wrapper
package.json#pi # merged Pi root compatibility manifest
Skills use Agent Bundler overlays for target-specific frontmatter, body, and
support-file changes. Target-wide preambles are composition entries in
agentbundle.json. Canonical source remains readable Markdown with YAML
frontmatter; Agent Bundler emits normalized JSON frontmatter.
Package membership is defined by src/.agentbundler/packages/*.json. Each
package lists exact skill and agent asset paths. Root marketplace files are
routing wrappers only: their entries point into dist/<target> and contain no
independent package trees. Do not edit dist/ or give the wrappers independent
metadata.
| Target | Output | Package contract |
|---|---|---|
| Claude Code | dist/claude/<package>/ | Marketplace packages, agents, and hooks |
| Codex CLI | dist/codex/<package>/ | Plugin packages plus .codex/agents/*.toml profiles |
| Pi | dist/pi/ | Aggregate package, typed hooks, and native extensions |
| GitHub Copilot | dist/copilot/<package>/ | Marketplace packages, agents, and hooks |
| Cursor | dist/cursor/<package>/ | Marketplace packages, agents, and supported hooks |
| Grok Build | dist/grok/<package>/ | Marketplace packages, agents, and hooks |
| Gemini CLI | none | Retired |
agbun package --root . --out DIR creates deterministic, target-native release
archives:
cc-thingz-claude.tar.gzcc-thingz-codex.tar.gzcc-thingz-pi.tgzcc-thingz-copilot.tar.gzcc-thingz-cursor.tar.gzcc-thingz-grok.tar.gzThe release workflow attaches all six files. Each archive expands directly to
the native package or marketplace root shown above. The Codex archive also
includes separate .codex/agents/*.toml profiles; they are not plugin contents.
Installation and marketplace registration use the target vendor's CLI; Agent
Bundler does not mutate user configuration or publish to a vendor registry.
Compatibility manifests at the repository root preserve Git and local-path
installation while keeping dist/<target> canonical:
npx claudepluginhub alexei-led/cc-thingz --plugin dev-flowResearch, docs lookup, utility routing, skill authoring, instruction review, reasoning, and agent configuration audits
Lightweight spec loop: plan one slice, execute one task, checkpoint or close
Git worktrees, branch cleanup, hooks, secret scanning, config hygiene, and guardrails
Browser-based testing, validation, screenshots, recordings, and quick automation
Idiomatic development across C# /.NET, Go, Java/Kotlin, Python, Rust, TypeScript, shell, and web
Code review practices with technical rigor and verification gates. Use for receiving feedback, requesting code-reviewer subagent reviews, or preventing false completion claims in pull requests.
Development autopilot — 28 lifecycle skills + 3 methodology agents + 25 hooks (10 default-on, 15 opt-in) enforcing Three Red Lines discipline. Standalone-capable orchestration that coexists with Superpowers.
Cross-agent development skills, hooks, orchestration, and optional custom-agent adapters for Claude Code and Codex
Universal Claude Code workflow with specialized agents, skills, hooks, and output styles for any software project. Includes orchestrator, code-reviewer, debugger, docs-writer, security-auditor, refactorer, and test-architect agents.
Unified Claude Code plugin merging superpowers workflows (TDD, debugging, planning) with everything-claude-code productivity (agents, learning, hooks, rules)
Internal workflows used by Cursor developers for CI, code review, and shipping. Covers the full dev loop: CI monitoring and fixing, PR creation, merge conflicts, smoke tests, compiler checks, code cleanup, and work summaries.