A Claude Code toolbox for AI-native development — commands, agents, skills, and scripts designed to compress the full SDLC cycle.
ai-dev-tools runs interactively inside Claude Code: you invoke a command, Claude orchestrates agents over your codebase, and you stay in the loop at every decision point. For a headless, fully automated pipeline that runs without human input between steps (GitHub Actions, Qwen3-32B via Groq), see autonomous-dev-loop.
The human is a gate, not a relay. Commands orchestrate agents; agents do one thing well; skills shape how they reason.
GitHub issue → /issue-code-generation → ticket-analyst → code-builder → code-reviewer → human merge gate
input command agent agent agent approval
Example run:
# In your terminal
$ gh issue view 42
title: Add rate limiting to API gateway
body: As a DevOps engineer, I want requests capped per client key...
# In Claude Code
> /issue-code-generation 42
[ticket-analyst] Parsing issue #42...
→ DONE — brief: rate-limiting middleware, scope: api-gateway/middleware/
[code-builder] Generating patch...
→ DONE — 3 files changed, tests included
[code-reviewer] Validating against acceptance criteria...
→ NEEDS_REVIEW — missing error code on quota exceeded
Review report → ~/dev/pr-reviews/42-rate-limiting.md| Primitive | Role | How it works |
|---|---|---|
| Skills | Passive context | Conventions, patterns, rules loaded automatically via CLAUDE.md. Shape how the agent reasons without being called explicitly. |
| Agents | Execution units | Discrete, specialized, explicit I/O contracts. Do one thing well. Chainable via structured ### Status / ### Handoff blocks. |
| Commands | Orchestrators | Chain agents, invoke scripts, manage workflow state. Type /name in Claude Code to trigger a full pipeline. |
Every agent produces a structured output block — this makes them chainable without human interpretation between steps:
### Status
[DONE | BLOCKED | NEEDS_REVIEW] — one-line summary
### <Agent-specific section>
...findings, code, analysis...
### Handoff
Next step and what to pass forward| Invoke | Agents used | What it does |
|---|---|---|
/issue-code-generation [id] [--strict] |
ticket-analyst → code-builder → code-reviewer |
Full issue → code → AC validation pipeline. --strict activates critic-pair (code-challenger) before review |
/pr-review |
pr-analyst |
Review PR, write structured report to ~/dev/pr-reviews/ |
/pr-fixer |
code-builder |
Apply blocking fixes from an existing review file |
/ac-check [id] |
code-reviewer |
Validate code coverage against issue acceptance criteria |
/bug-seeker [id] |
— | Interactive investigation — issue, logs, code → diagnostic report |
/issue-notes [id] |
— | Generate technical overview, post as GitHub issue comment |
/demo-prep |
— | Feature description → slide-ready sprint demo content |
/token-audit [days] |
— | Audit Claude Code token usage — trends, model breakdown, command adoption |
/check-releases |
— | List repos with main changes not yet in a release |
/sync-ai-dev-tools |
— | Sync commands, agents, and prompts from this repo to ~/.claude |
| Agent | Input | Output |
|---|---|---|
ticket-analyst |
Raw GitHub issue | Concise implementation brief |
code-builder |
Implementation brief | Smallest correct patch |
code-reviewer |
Diff + context | Bugs, regressions, risks, missing tests |
pr-analyst |
PR diff | Structured review summary |
doc-builder |
Repo/branch context | Documentation |
impact-analyst |
Proposed change | Cross-repo blast radius analysis |
| Skill | Loaded when | What it enforces |
|---|---|---|
scope-guard.md |
Always | Changes stay inside the authorized file perimeter |
wiki-first.md |
Always | Wiki/docs lookup before any business logic implementation |
git-conventions.md |
Any git op | Commit format, branching strategy, merge rules |
branch-pr.md |
Any git op | Branch, commit, and PR naming conventions |
dotnet-repository.md |
C# work | Repository/Handler/Controller patterns (Dapper) |
vue-ui.md |
Vue work | Component structure, store, i18n |
vue-service.md |
Vue work | Vuex service and store conventions |
Skills are loaded by the global
CLAUDE.mdat workspace root, which acts as a navigation orchestrator — it routes to per-repoCLAUDE.mdfiles and injects the relevant skills based on file paths being touched.
| Script | What it does | Usage |
|---|---|---|
onboarding.mjs |
Full setup — copy workspace config, create skills junction, deploy commands and agents | CLI |
sync-claude.mjs |
Incremental sync from ai-dev-tools → ~/.claude (reports new/updated/extra) |
CLI / via /sync-ai-dev-tools |
gh-get-issue.mjs |
Fetch GitHub issue by number → JSON | CLI / via commands |
gh-get-pr.mjs |
Fetch PR by number or source branch | CLI / via commands |
gh-get-pr-threads.mjs |
Fetch reviewer comment threads for a PR | CLI / via commands |
gh-post-comment.mjs |
Post a comment to a GitHub issue | CLI / via commands |
gh-my-issues.mjs |
List issues assigned to current user | CLI |
token-audit.mjs |
Aggregate token usage from Claude Code JSONL session files | via /token-audit |
update-repos.mjs |
Pull latest on all configured repos | CLI |
list-files.mjs |
Recursive numbered file listing | CLI |
ai-dev-tools/
├── agents/ Specialized subagents — explicit I/O contracts, chainable
├── commands/ Slash commands — type /name in Claude Code to invoke a pipeline
├── skills/ Stack conventions — loaded automatically via CLAUDE.md
├── scripts/ GitHub CLI, token auditing, sync utilities
├── prompts/ Standalone prompt templates for manual use
├── docs/
│ ├── adr/ Architecture Decision Records
│ └── commands/ Reference docs for each slash command
└── workspace/ Config files deployed to your dev root on setup
├── CLAUDE.md Workspace orchestrator
└── .claude/CLAUDE.md Execution rules
- Node ≥ 20
- Claude Code CLI — requires an Anthropic account with Claude Code access (paid plan or active quota)
- GitHub CLI authenticated
- Git
git clone https://github.com/koydas/ai-dev-tools ~/dev/ai-dev-tools
node ~/dev/ai-dev-tools/scripts/onboarding.mjsThen open .env and set gh_token (scope: repo, read:org). The file is git-ignored.
node ~/dev/ai-dev-tools/scripts/sync-claude.mjsWindows? All scripts target PowerShell-compatible paths. The onboarding script creates a junction for
skills/rather than a symlink.
See CONTRIBUTING.md for how to add agents and commands.
| Repo | What it demonstrates |
|---|---|
autonomous-dev-loop |
Fully autonomous GitHub-native SDLC — Issue → AI coder → PR → AI reviewer → iterative loop → human merge gate. Groq-backed, GitHub Actions orchestration, prompt files loaded at runtime. |
fullstack-pilot |
Polyglot multi-service stack: React/Vite, Node/Express, Flask, .NET 8 — across MongoDB, PostgreSQL, and SQL Server. Includes CI/CD workflows, ADRs, and a Mermaid architecture diagram. |