/aitask-pick
Select and implement the next task — the central development skill
aitasks provides code agent skills that automate the full task lifecycle. Claude Code is the source of truth (/aitask-*); Gemini CLI and OpenCode use the same slash-command style, while Codex CLI wrappers use $aitask-*.
Claude Code / Codex CLI / Gemini CLI / OpenCode (agent availability depends on installed wrappers).
Start here:
/aitask-pickis the hub skill — it drives the full pick → plan → implement → review → archive lifecycle. Read that first, then branch based on use case: creation with/aitask-explore, batch/remote with/aitask-pickremor/aitask-pickweb, review with/aitask-reviewand/aitask-qa.
Multi-agent support: Codex CLI and Gemini CLI wrappers are installed in
.agents/skills/; OpenCode wrappers are installed in.opencode/skills/. Invoke skills with/aitask-pick,/aitask-create, etc. in Claude Code, Gemini CLI, and OpenCode, or with$aitask-pick,$aitask-create, etc. in Codex CLI. Runait setupto install the wrappers detected for your agent. Interactive Codex skills require plan mode becauserequest_user_inputis only available there; OpenCode uses nativeskilland nativeask, so this caveat does not apply there. However, if OpenCode is launched in plan mode, its read-only tool restriction may cause task locking to be skipped — see Known Issues.
Run from the project root. aitasks expects to be invoked from the directory containing
.git/— the root of your project’s git repository. All skills use relative paths (e.g.,./.aitask-scripts/aitask_ls.sh) and expect to start there. Launching an agent from a subdirectory can break path-based permissions and wrapper assumptions, and in Claude Code it will also trigger repeated permission prompts. Alwayscdthere before launching your agent.
Core workflow skills for picking and implementing tasks.
| Skill | Description |
|---|---|
/aitask-pick | The central skill — select and implement the next task (planning, branching, implementation, archival) |
/aitask-pickrem | Autonomous remote variant of /aitask-pick — zero interactive prompts, profile-driven |
/aitask-pickweb | Sandboxed variant for Claude Code Web — local metadata storage, requires follow-up with /aitask-web-merge |
/aitask-web-merge | Merge completed Claude Web branches to main and archive task data |
Create, organize, and wrap tasks.
| Skill | Description |
|---|---|
/aitask-create | Create tasks interactively via code agent prompts |
/aitask-explore | Explore the codebase interactively, then create a task from findings |
/aitask-fold | Identify and merge related tasks into a single task |
/aitask-revert | Revert changes associated with completed tasks — fully or partially |
/aitask-wrap | Wrap uncommitted changes into an aitask with retroactive documentation |
Import external work and contribute changes back.
| Skill | Description |
|---|---|
/aitask-pr-import | Import a pull request as an aitask with AI-powered analysis and implementation plan |
/aitask-contribute | Turn local changes into structured contribution issues for upstream repos |
/aitask-contribution-review | Analyze contribution issues for duplicates and overlaps, then import as tasks |
Review code and manage review guides.
| Skill | Description |
|---|---|
/aitask-explain | Explain files: functionality, usage examples, and code evolution traced through aitasks |
/aitask-qa | Run QA analysis on any task — discover tests, run them, identify gaps, and create follow-up test tasks |
/aitask-review | Review code using configurable review guides, then create tasks from findings |
/aitask-reviewguide-classify | Classify a review guide by assigning metadata and finding similar guides |
/aitask-reviewguide-merge | Compare two similar review guides and merge, split, or keep separate |
/aitask-reviewguide-import | Import external content as a review guide with proper metadata |
Settings, statistics, and model management.
| Skill | Description |
|---|---|
/aitask-refresh-code-models | Research latest AI code agent models and update model configuration files |
/aitask-stats | View completion statistics |
/aitask-changelog | Generate changelog entries from commits and plans |
| Verified Scores | How skill satisfaction ratings accumulate into verified model scores |
Next: Command Reference
Select and implement the next task — the central development skill
Pick and implement a task in remote/non-interactive mode — zero prompts, profile-driven
Pick and implement a task on Claude Code Web — sandboxed skill with local metadata storage
Merge completed Claude Web branches to main and archive task data
Explore the codebase interactively, then create a task from findings
Analyze a pull request and create an aitask with implementation plan
Turn local changes into structured contribution issues for the aitasks framework or the current project repo
Analyze contribution issues for duplicates and overlaps, then import as grouped or single tasks
Identify and merge related tasks into a single task
Revert changes associated with completed tasks — fully or partially
Create a new task file interactively via code agent prompts
Wrap uncommitted changes into an aitask with retroactive documentation and traceability
View task completion statistics via a code agent
Explain files: functionality, usage examples, and code evolution traced through aitasks
Research latest AI code agent models and update model configuration files
Register a known code-agent model in models_
Generate a changelog entry from commits and archived plans
Review code using configurable review guides, then create tasks from findings
Run QA analysis on any task — discover tests, run them, identify gaps, and create follow-up test tasks
Classify a review guide by assigning metadata and finding similar guides
Compare two similar review guides and merge, split, or keep separate
Import external content as a review guide with proper metadata
How skill satisfaction ratings accumulate into verified model scores