By amingclawdev
Enforce graph-first governance workflows in Claude Code sessions with backlog tracking, duplicate detection, evidence collection, subagent observability, and access control gates, backed by a remote governance MCP server.
Explicit Aming Claw onboarding and launcher entry. Use for `/aming-claw:aming-claw-launcher`, "aming-claw launcher", "onboard me to Aming Claw", "start/open dashboard/status", install-and-start requests, fresh project registration, or any onboarding question. Defer graph, backlog, semantic, manual-fix, or chain implementation work to `/aming-claw:aming-claw` after this state machine reaches the fixed first-value steps.
Use when a user wants to capture raw requirements, keep talking without dispatching work, review a batch of captured requirements, or promote confirmed requirements into Aming Claw backlog rows from the Project Inbox.
Use when reviewing user-facing Aming Claw flows against the bundled ue_audit.v1 contract, especially ordinary non-technical builder flows where request and state visibility matter.
Public demo for Vibe Queue: keep talking while agents work. Use when a user asks to run, preview, or collect evidence for a mid-implementation requirement being handled by the current Claude Code or Codex observer session.
Public demo for Backlog Duplicate: a new requirement overlaps existing backlog work, and the observer asks whether to merge, supersede, or keep it separate. Use when a user asks to run, preview, or collect duplicate backlog evidence with the current Claude Code or Codex observer session.
Matches all tools
Hooks run on every tool call, not just specific ones
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.
Your AI agent and you, sharing the same dashboard.
Open source workspace for AI-coded development. See what AI is touching in real-time, audit every change, review proposals before they land in your codebase. Multi-language (Python/TypeScript), MCP-native, local-first.

Aming Claw is a graph-governed control plane for AI-agent code review. The claim is narrow: not total program correctness, not human-free review, and not free first-build cost on huge monorepos. The V1 loop is a reusable project fact layer: commit-bound graph state, typed AI proposals, review gates, durable repair rules, and reconcile after code or rules change.
flowchart TD
Human["Human reviewer"] --> UI["Dashboard"]
Agent["AI agent"] --> MCP["MCP tools"]
UI --> Gov["Governance control plane"]
MCP --> Gov
Gov --> Backlog["Backlog<br/>intent + work ledger"]
Gov --> Review["Review Queue<br/>accept / reject proposals"]
Gov --> Graph["Commit-bound graph<br/>files, functions, tests, docs, config"]
Agent --> Proposal["Typed AI proposals<br/>semantic / graph / config / backlog"]
Proposal --> Review
Code["Committed code"] --> Reconcile["Reconcile<br/>derive review state"]
Rules["Hints + config + rules"] --> Reconcile
Review --> Events["Accepted semantic events"]
Events --> Reconcile
Reconcile --> Graph
Reconcile --> Semantics["Semantic projection<br/>current / stale / missing"]
Graph --> Context["Scoped review context"]
Semantics --> Context
Backlog --> Context
The important boundary: AI proposals are not trusted state. Committed code, source-controlled hints/config/rules, and accepted semantic events are source; graph snapshots, semantic projections, review queues, and test/doc/config bindings are derived state.
Start with the AI host you use. The longer requirements, raw installer commands, and troubleshooting notes are in Install Details.
Ask Codex for the complete one-shot path. This installs the plugin/runtime, starts local governance, and opens the dashboard:
One-shot install and open dashboard for Aming Claw from https://github.com/amingclawdev/aming-claw
If you only want to refresh the local plugin package, use the install-only command instead. Install-only does not start the long-running governance service and does not open the dashboard:
aming-claw plugin install https://github.com/amingclawdev/aming-claw
Reload Codex or open a new Codex session after install. First-run startup and verification steps are in Install Details.
Paste this once — Claude bootstraps the plugin end-to-end:
Install aming-claw end-to-end from https://github.com/amingclawdev/aming-claw:
1. Run `/plugin marketplace add https://github.com/amingclawdev/aming-claw`
2. Run `/plugin install aming-claw@aming-claw-local`
3. pip install -e the marketplace clone at
~/.claude/plugins/marketplaces/aming-claw-local
(Windows: %USERPROFILE%\.claude\plugins\marketplaces\aming-claw-local)
4. Start `aming-claw start` in a background terminal
5. Run `aming-claw open` to launch the dashboard
6. Remind me to reload Claude Code so the plugin's MCP tools and skills load
Steps 1–2 only copy the skill files; pip install adds the Python runtime,
aming-claw start boots the local governance service, and aming-claw open
launches the dashboard. After reloading, phrases like "install and start
aming-claw" or "one-shot install" trigger the launcher skill's one-shot
mode for re-bootstrap in future sessions. First-run troubleshooting and
raw installer scripts are in Install Details. The compact
onboarding state machine is /aming-claw:aming-claw-launcher; the full
first-run schema and route-gate notes are in
docs/onboarding.md.
npx claudepluginhub amingclawdev/aming-claw --plugin aming-clawHarness for Claude Code — skills, /harness:* slash commands, persona subagents, lifecycle hooks, and MCP tools without per-repo `harness setup`. Sibling plugins exist for Cursor, Gemini CLI, and Codex.
Complete project development toolkit: 23 agents, 23 slash commands, 29 lifecycle hooks, and 69 reusable skills for Claude Code workflows
Governed workflow skills, reviewer agents, and enforcement hooks for govctl
Implementation planning, execution, and PR creation workflows with multi-agent collaboration
Agent Teams orchestration, governance hooks, multi-AI review, memento skill intelligence, and project management skills for Claude Code
Corca Workflow Framework — consolidated hooks and skill orchestration for structured development sessions