Menu
AI-powered developer workflows with Socratic discovery
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Outcome-first fix with a guided intake form — pick scope and probes from derived candidates, preview the contract, run with a verified receipt. Triggers on: attune fix, scoped fix, fix with receipt, outcome fix, fix intake.
Outcome-first fix with a guided intake form — pick scope and probes from derived candidates, preview the contract, run with a verified receipt. Triggers on: attune fix, scoped fix, fix with receipt, outcome fix, fix intake.
Spec-driven development — brainstorm, plan, review, and execute with quality gates. Triggers on: spec, brainstorm and build, plan and execute, idea to code, build from scratch.
Spec-driven development — brainstorm, plan, review, and execute with quality gates. Triggers on: spec, brainstorm and build, plan and execute, idea to code, build from scratch.
Developer workflow hub — routes to the right skill based on what you need. Triggers on: attune, what can attune do, what can you do, capabilities, where do I start, get started.
Outcome-first fix with a guided intake form — pick scope and probes from derived candidates, preview the contract, run with a verified receipt. Triggers on: attune fix, scoped fix, fix with receipt, outcome fix, fix intake.
| name | attune |
| description | AI-powered developer workflows with Socratic discovery |
Your AI-powered developer workflow assistant with Socratic discovery.
One command. Every workflow.
Type /attune and I'll guide you through questions to find the right workflow.
/attune # Start Socratic discovery
/attune "I need to fix a bug" # Natural language
/attune debug # Direct shortcut
When the user provides sufficient context inline, skip scoping questions and execute directly. This satisfies the Socratic requirement because the user's explicit args provide the scoping context.
Fast-path triggers (execute immediately):
/attune security-audit ./src/attune "review src/auth"--auto flag:
/attune commit --autoSocratic flow (ask questions first):
/attune (no args)/attune "fix something" (vague)Rule: If input contains BOTH an action AND a target,
proceed to execution. If either is missing or ambiguous,
use AskUserQuestion.
Debugging:
Code Review:
Refactoring:
Testing:
Coverage:
Security Audit:
Performance Audit:
Commit:
Pull Request:
Release:
Explain Code:
Generate Docs:
Feature Overview:
| Shortcut | Action |
|---|---|
/attune debug | Start debugging session |
/attune review | Code review |
/attune refactor | Refactoring session |
/attune test | Run tests |
/attune coverage | Coverage analysis |
/attune security | Security audit |
/attune commit | Create commit |
/attune pr | Create pull request |
/attune release | Prepare release |
/attune docs | Documentation |
/attune explain | Explain code |
Just describe what you need:
ALWAYS use AskUserQuestion to scope and confirm before executing any workflow. NEVER skip straight to running commands.
If invoked without arguments (/attune), use AskUserQuestion to ask what the user is trying to accomplish.
Once the goal is identified, use AskUserQuestion to narrow scope. Examples:
Only after scoping via AskUserQuestion, execute the appropriate CLI command.
When the user types a shortcut, still ask a scoping question before executing:
| Input | CLI Command |
|---|---|
/attune security | uv run attune workflow run security-audit |
/attune test | uv run pytest |
/attune coverage | uv run pytest --cov=src --cov-report=term-missing |
/attune perf | uv run attune workflow run perf-audit |
/attune review | uv run attune workflow run code-review |
/attune bug-predict | uv run attune workflow run bug-predict |
/attune test-gen | uv run attune workflow run test-gen |
/attune commit | Use git to stage and commit changes |
/attune pr | Use gh to create a pull request |
/attune release | uv run attune workflow run release-prep |
/attune debug | Start interactive debugging session |
/attune refactor | Analyze code and suggest refactoring |
/attune docs | Generate documentation |
/attune explain | Read and explain the specified code |
When the user provides natural language, map to the appropriate CLI command:
| Pattern | CLI Command |
|---|---|
| "security", "vulnerabilities", "audit" | uv run attune workflow run security-audit |
| "test", "tests", "run tests" | uv run pytest |
| "coverage", "test coverage" | uv run pytest --cov=src --cov-report=term-missing |
| "generate tests", "write tests" | uv run attune workflow run test-gen |
| "review", "code review" | uv run attune workflow run code-review |
| "performance", "perf", "bottleneck" | uv run attune workflow run perf-audit |
| "bugs", "predict bugs" | uv run attune workflow run bug-predict |
| "release", "ship", "publish" | uv run attune workflow run release-prep |
IMPORTANT: When arguments are provided, DO NOT just display documentation. Use AskUserQuestion to scope, THEN execute the CLI command.
# Workflows
uv run attune workflow run security-audit --path <target>
uv run attune workflow run perf-audit --path <target>
uv run attune workflow run bug-predict --path <target>
uv run attune workflow run code-review --path <target>
uv run attune workflow run test-gen --path <target>
uv run attune workflow run release-prep
# Testing
uv run pytest
uv run pytest --cov=src --cov-report=term-missing
uv run pytest -k "test_name"
# Telemetry
uv run attune telemetry show
Socratic over menus. I ask "What are you trying to accomplish?" not "Which tool do you want?" This helps you think about your actual goal.
Teaching over telling. I help you understand why, not just what.
Questions before actions. ALWAYS use AskUserQuestion to guide users through decisions at every step — goal identification, scoping, and confirmation. Never assume scope or jump to execution. This is the #1 rule of the Attune workflow experience.