Stable on aitasks

/aitask-pick

Mon, 01 Jan 0001 00:00:00 +0000

The central skill of the aitasks framework. This is a full development lifecycle skill that manages the complete task lifecycle from selection through implementation, review, and archival.

Usage:

/aitask-pick # Interactive task selection from prioritized list
/aitask-pick 10 # Directly select parent task t10
/aitask-pick 10_2 # Directly select child task t10_2

Note: Must be run from the project root directory. See Skills overview for details.

Codex CLI note: In Codex wrappers, after implementation, most of the times you will need to explicitly tell the agent to continue the workflow because request_user_input is only available in plan mode. Example prompts: Good, now finish the workflow or Good, now continue.

Kanban Board

Mon, 01 Jan 0001 00:00:00 +0000

The ait board command launches an interactive terminal-based kanban board for managing your tasks visually. Built with Textual, it provides a full-featured TUI with columns, task cards, inline metadata editing, git integration, and keyboard-driven navigation.

The ait board kanban view with task cards organized into columns

How-To Guides

Mon, 01 Jan 0001 00:00:00 +0000

How to Organize Tasks into Columns

Moving a task to a different column:

Focus the task card using arrow keys
Press Shift+Right to move it to the next column, or Shift+Left to move it to the previous column

The task is appended to the end of the target column. Column order follows the configured order, with “Unsorted / Inbox” on the far left. Collapsed columns are skipped when moving tasks.

How-To Guides

Mon, 01 Jan 0001 00:00:00 +0000

How to Navigate Files in the Tree

Press Tab to focus the file tree (if not already focused)
Use Up / Down arrows to move between files and directories
Press Enter or click a file to open it in the code viewer
Directories expand and collapse as you navigate into them

The tree shows only git-tracked files, automatically excluding __pycache__, node_modules, and .git directories. Dotfiles (like .gitignore) are included.

How to Navigate Code

Once a file is open in the code viewer:

How-To Guides

Mon, 01 Jan 0001 00:00:00 +0000

How Minimonitor Is Auto-Spawned

Minimonitor is meant to be auto-spawned — you almost never start it yourself. Every ait TUI that launches a new code agent window also creates a minimonitor split next to it:

ait board — when you pick a task and launch its agent (action menu or agent command screen).
ait codebrowser — when you launch an agent from a code file or the history screen.
ait monitor — when you press n on an agent card to pick its next ready sibling task, which creates a new agent window.
The TUI switcher’s explore launch — when it creates an agent window for an explore target.

In every case the flow is the same: the launching TUI creates a new tmux window named agent-..., then the auto-spawn helper creates a horizontal right-split inside that window and runs ait minimonitor in it. The helper skips the split if the window name does not start with the configured agent prefix (default agent-) or if a monitor/minimonitor is already running in the window.

How-To Guides

Mon, 01 Jan 0001 00:00:00 +0000

How to Start the Monitor

Recommended — via ait ide:

ait ide

This is the one-command path to the ait tmux IDE. ait ide resolves the tmux session name from tmux.default_session in project_config.yaml (defaulting to aitasks), creates or attaches to that session, and opens a monitor window inside it. Because it always passes an explicit session name, the session-rename dialog never fires.

Standalone — from inside an existing tmux session:

ait monitor

Run this from within a tmux session you already have open. Monitor attaches to the current session.

Monitor

Mon, 01 Jan 0001 00:00:00 +0000

The ait monitor command launches an interactive TUI that shows every pane in the current tmux session, categorized as code agents, TUIs, or other panes, with a live preview of the focused pane and keystroke forwarding. It is the dashboard of the ait tmux-based development environment: from a single window you can watch agents work, jump to any other TUI, and interact with running processes without leaving the monitor.

The ait monitor dashboard with categorized panes and live preview.

Minimonitor

Mon, 01 Jan 0001 00:00:00 +0000

ait minimonitor is a narrow (~40 column) sidebar TUI that lists every running code agent across every aitasks tmux session on the current tmux server, with idle indicators and a companion-pane focus model. It is the agents-only cousin of ait monitor: no preview panel, no TUI/other pane categories — just the running agents in a compact column designed to sit next to a code pane while you work.

Minimonitor is meant to be auto-spawned alongside every code agent you launch from the ait TUIs. You rarely need to start it yourself — whenever a new agent window is created, the launching TUI also splits a minimonitor pane next to it, and minimonitor closes itself automatically when the agent pane exits. Manual launch via ait minimonitor is supported but is an escape hatch rather than the primary workflow.

/aitask-explore

Mon, 01 Jan 0001 00:00:00 +0000

Explore the codebase interactively with guided investigation, then create a task from findings. This skill bridges the gap between “I think something needs work” and a well-defined task with context.

Usage:

/aitask-explore [--profile <name>]

The optional --profile <name> argument overrides execution-profile selection for this invocation, mirroring /aitask-pick --profile.

Note: Must be run from the project root directory. See Skills overview for details.

Codex CLI note: When continuing from this skill into implementation, in Codex wrappers, after implementation, most of the times you will need to explicitly tell the agent to continue the workflow because request_user_input is only available in plan mode. Example prompts: Good, now finish the workflow or Good, now continue.

Code Browser

Mon, 01 Jan 0001 00:00:00 +0000

The ait codebrowser command launches an interactive terminal-based code browser for exploring project files with task-aware annotations. Built with Textual, it provides syntax-highlighted file viewing, a git-aware file tree, and an annotation gutter that maps lines of code to the aitasks that introduced them — powered by the explain data pipeline.

The ait codebrowser with file tree (left) and syntax-highlighted code viewer (right)

How-To Guides

Mon, 01 Jan 0001 00:00:00 +0000

Mouse Support

The Settings TUI supports full mouse interaction in addition to the keyboard shortcuts:

Click a tab name in the tab bar — switch to that tab (alternative to a / b / c / t / m / p).
Click a field row — focus it; press Enter / Space to edit or cycle the value.
Click on-screen action buttons — Save Profile, Commit, Save Board Settings, Save Project Config, New Profile, and dialog buttons are all clickable, no keyboard equivalent required.
Scroll wheel — scroll long tab content (Profiles, Models, Project Config).

All keyboard actions documented below remain available.

Feature Reference

Mon, 01 Jan 0001 00:00:00 +0000

Keyboard Shortcuts

Key	Action	Context
`q`	Quit the application	Global
`Tab`	Toggle focus between search box and board	Global
`Escape`	Return to board from search / dismiss modal	Global
`Up`	Navigate to previous task in column	Board
`Down`	Navigate to next task in column	Board
`Left`	Navigate to previous column	Board
`Right`	Navigate to next column	Board
`Enter`	Open task detail dialog	Board (focused card)
`r`	Refresh board from disk	Board
`s`	Sync task data with remote	Board
`O`	Open board options/settings dialog	Board
`a`	Switch to All view (show all tasks)	Board
`g`	Switch to Git view (show git-linked tasks)	Board
`i`	Switch to Implementing view (show implementing tasks + context)	Board

Task Operations

Key	Action	Context
`Shift+Right`	Move task to next column (skips collapsed)	Board (parent cards only)
`Shift+Left`	Move task to previous column (skips collapsed)	Board (parent cards only)
`Shift+Up`	Swap task with one above	Board (parent cards only)
`Shift+Down`	Swap task with one below	Board (parent cards only)
`Ctrl+Up`	Move task to top of column	Board (parent cards only)
`Ctrl+Down`	Move task to bottom of column	Board (parent cards only)
`n`	Create a new task	Board
`x`	Toggle expand/collapse child tasks	Board (parent or child card)
`c`	Commit focused modified task	Board (shown when task is modified)
`C`	Commit all modified tasks	Board (shown when any task is modified)
`p`	Pick the focused task (start implementation)	Board (context-dependent — shown when task is pickable)
`b`	Launch brainstorm for the focused task	Board (context-dependent — shown when task is brainstormable)

Column Operations

Key	Action	Context
`Ctrl+Right`	Move column one position right	Board
`Ctrl+Left`	Move column one position left	Board
`X` (Shift+X)	Toggle collapse/expand for focused card’s column	Board (focused card)
`Ctrl+Backslash`	Open command palette	Global
Click `▼` / `▶`	Toggle column collapse/expand	Column header
Click `✎`	Open column edit dialog	Column header

Key	Action	Context
`Up`	Focus previous field	Inside modal dialogs
`Down`	Focus next field	Inside modal dialogs
`Left`	Cycle to previous option	On CycleField
`Right`	Cycle to next option	On CycleField
`Enter`	Activate focused button / navigate to linked task	Inside modal dialogs
`Escape`	Close the dialog	Inside modal dialogs

Task Card Anatomy

┌─────────────────────────────────┐ ← Border color = priority
│ t47 * playlists support │ ← Task number (cyan), * if modified (orange), title (bold)
│ 💪 medium | 🏷️ ui,api | GH | PR:GH | @alice │ ← Effort, labels, issue/PR indicator, contributor
│ 🔒 alice@example.com │ ← Lock indicator (if locked)
│ 🚫 blocked | 👤 alice │ ← Status/blocked, assigned to
│ 🔗 t12, t15 │ ← Blocking dependency links
│ 📎 folded into t42 │ ← Folded indicator (if applicable)
│ 👶 3 children │ ← Child task count (if parent)
└─────────────────────────────────┘

Not all lines are shown on every card — lines only appear when the corresponding data exists.

Feature Reference

Mon, 01 Jan 0001 00:00:00 +0000

Keyboard Shortcuts

Application

Key	Action	Context
`q`	Quit the application	Global
`Tab`	Cycle focus between file tree, code viewer, and detail pane	Global
`r`	Refresh explain annotations for current file’s directory	Global
`t`	Toggle annotation gutter visibility	Global
`g`	Open go-to-line dialog	Global
`e`	Launch the configured code agent for explain on the current file	Global
`d`	Toggle detail pane visibility	Global
`D`	Toggle detail pane between default and expanded width	Global
`h`	Toggle completed tasks history view	Global
`H`	Open history screen navigated to the task at cursor	Global (requires annotated line)

History Screen

Key	Action	Context
`h` / `Escape`	Return to code browser	History screen
`v`	Toggle task/plan content view	History screen
`l`	Open label filter dialog	History screen
`Tab`	Cycle focus between list and detail panes	History screen
`Left`	Move focus to list pane (cycles task list / recently opened)	History screen
`Right`	Move focus to detail pane	History screen
`Up` / `Down`	Navigate between focusable fields	History detail
`Enter`	Open link, select task, or navigate to file (context-dependent)	History detail
`s`	Open sibling task picker (on child tasks)	History detail
`a`	Launch QA agent for the selected task	History detail

Label Filter Dialog

Key	Action	Context
`Escape`	Cancel and close dialog	Dialog
`o`	Confirm selection (OK)	Dialog
`r`	Reset filter (show all)	Dialog

Sibling Picker Dialog

Key	Action	Context
`Escape`	Cancel and close dialog	Dialog
`Enter`	Select sibling task	Dialog

Code Viewer

Key	Action	Context
`Up`	Move cursor up one line	Code viewer
`Down`	Move cursor down one line	Code viewer
`Shift+Up`	Extend selection upward	Code viewer
`Shift+Down`	Extend selection downward	Code viewer
`Escape`	Clear selection	Code viewer
`n`	Create a task with `file_references` seeded from the selection or cursor line	Code viewer
`PageUp`	Move cursor up by one screen	Code viewer
`PageDown`	Move cursor down by one screen	Code viewer

Go-to-Line Dialog

Key	Action	Context
`Enter`	Jump to entered line number	Dialog
`Escape`	Cancel and close dialog	Dialog

Mouse Interactions

Action	Effect
Click on file tree entry	Select and open file
Click in code viewer	Position cursor at clicked line
Drag in code viewer	Select line range
Scroll wheel in code viewer	Scroll content

Annotation Data Pipeline

The codebrowser uses the same explain data pipeline as /aitask-explain:

Feature Reference

Mon, 01 Jan 0001 00:00:00 +0000

Keyboard Shortcuts

Key	Action	Context
`Tab`	Cycle focus to the next zone (pane list ↔ preview)	Global
`Shift+Tab`	Cycle focus to the previous zone	Global
`Up`	Focus the previous card in the pane list	Pane list zone
`Down`	Focus the next card in the pane list	Pane list zone
`q`	Quit monitor	Global

Pane Interaction

Key	Action	Context
`Enter`	Send an `Enter` keystroke to the focused tmux pane	Pane list zone
`Enter`	Send an `Enter` keystroke to the focused tmux pane	Preview zone
Any other key	Forwarded to the focused tmux pane (characters, Ctrl-combos, arrows, Escape)	Preview zone
`s`	Switch tmux focus to the focused pane (`tmux switch-client`)	Pane list zone
`i`	Show the task detail dialog for the focused agent pane (requires a task ID in the window name)	Pane list zone
`k`	Kill the focused pane after confirmation (`tmux kill-pane`)	Pane list zone
`n`	Pick the next ready sibling task for the focused agent pane	Pane list zone
`R`	Restart the task running in the focused agent pane	Pane list zone
`L`	Open the log for the focused pane in a separate viewer	Pane list zone

Monitor Controls

Key	Action	Context
`j`	Open the TUI switcher overlay	Global
`r`	Refresh the pane list and preview immediately	Global
`F5`	Refresh the pane list and preview immediately (alias for `r`, hidden in footer)	Global
`z`	Cycle the preview size through S / M / L presets	Global
`t`	Scroll the preview to its tail (newest output)	Global
`a`	Toggle auto-switch mode (automatically focus idle agents needing attention)	Global
`M`	Toggle the multi-session view ON/OFF (see Multi-session view)	Global

Note: In the preview zone, every keystroke that is not handled by a global binding is forwarded to the tmux pane via tmux send-keys. Special keys (Enter, Escape, Backspace, arrows, Space, Delete, Home, End, PageUp/Down) and Ctrl-combinations are translated; regular characters are sent literally.

/aitask-pr-import

Mon, 01 Jan 0001 00:00:00 +0000

Analyze pull requests from GitHub, GitLab, or Bitbucket using AI-powered code review, then create a well-structured aitask with contributor attribution. This skill bridges external contributions and the aitasks workflow — instead of merging PRs directly, it extracts the intent and approach, validates them against the codebase, and produces a task ready for implementation.

Usage:

/aitask-pr-import

Note: Must be run from the project root directory. See Skills overview for details.

Codex CLI note: When continuing from this skill into implementation, in Codex wrappers, after implementation, most of the times you will need to explicitly tell the agent to continue the workflow because request_user_input is only available in plan mode. Example prompts: Good, now finish the workflow or Good, now continue.

/aitask-contribute

Mon, 01 Jan 0001 00:00:00 +0000

Use /aitask-contribute to turn local changes into a structured contribution issue without going through the usual fork, branch, and pull request flow. You can use it to contribute improvements back to the aitasks framework, or to contribute changes to the current project repository when that project uses the aitasks framework.

Usage:

/aitask-contribute

Note: Must be run from the project root directory. Requires the platform CLI installed and authenticated: gh for GitHub (default), glab for GitLab, or bkt for Bitbucket. See Skills overview for details.

/aitask-contribution-review

Mon, 01 Jan 0001 00:00:00 +0000

Use /aitask-contribution-review to review incoming contribution issues with AI-powered duplicate detection, overlap analysis, and merge recommendations. The skill fetches the target issue, finds related contributions, analyzes code diffs, and helps you decide whether to merge, import individually, fold into existing tasks, or update an existing task directly.

Usage:

/aitask-contribution-review 42 # Review a specific issue
/aitask-contribution-review # List open contribution issues and choose

Note: Must be run from the project root directory. Requires the platform CLI installed and authenticated: gh for GitHub (default), glab for GitLab. The skill uses a helper script that encapsulates all platform-specific API calls. See Skills overview for details.

/aitask-fold

Mon, 01 Jan 0001 00:00:00 +0000

Identify and merge related tasks into a single task, then optionally execute it. This skill provides the same folding capability as /aitask-explore but as a standalone skill — no codebase exploration required.

Usage:

/aitask-fold # Interactive: discover and fold related tasks
/aitask-fold 106,108,112 # Explicit: fold specific tasks by ID

Note: Must be run from the project root directory. See Skills overview for details.

Codex CLI note: When continuing from this skill into implementation, in Codex wrappers, after implementation, most of the times you will need to explicitly tell the agent to continue the workflow because request_user_input is only available in plan mode. Example prompts: Good, now finish the workflow or Good, now continue.

Reference

Mon, 01 Jan 0001 00:00:00 +0000

Keyboard Shortcuts

Global

Key	Action
a	Switch to Agent Defaults tab
b	Switch to Board tab
c	Switch to Project Config tab
t	Switch to Tmux tab
m	Switch to Models tab
p	Switch to Profiles tab
e	Export all configs
i	Import configs
r	Reload all configs from disk
q	Quit

Within Tabs

Key	Action	Context
Enter / Space	Edit field or cycle value	Agent Defaults, Board, Profiles
d / Delete	Remove user override	Agent Defaults
?	Toggle field description (summary/expanded)	Profiles
Escape	Close dialog or cancel	Modals

Mouse Interactions

Action	Effect
Click a tab name	Switch to that tab
Click a field row	Focus the row (then Enter / Space edits or cycles)
Click action buttons (Save, Commit, New Profile, etc.)	Activate the button
Scroll wheel	Scroll the focused tab content

Tabs

Tab	Shortcut	Editable	Description
Agent Defaults	a	Yes	Default agent/model per operation, project and user layers
Board	b	Partially	Columns (read-only), user settings (editable)
Project Config	c	Yes	Shared values from `project_config.yaml` such as coauthor domain and build verification
Tmux	t	Yes	Tmux integration settings (session name, split direction, monitor options, git TUI)
Models	m	No	Available models per agent with verified scores
Profiles	p	Yes	Execution profiles that pre-answer workflow questions

Agent Defaults Operations

Operation	Description
`task-pick`	Model used for picking and implementing tasks
`explain`	Model used for explaining/documenting code
`batch-review`	Model used for batch code review operations
`raw`	Model used for direct/ad-hoc code agent invocations (passthrough mode)

Configuration Files

File	Scope	Editable via TUI	Description
`aitasks/metadata/codeagent_config.json`	Project	Yes (Agent Defaults)	Default agent/model per operation
`aitasks/metadata/codeagent_config.local.json`	User	Yes (Agent Defaults)	Per-user overrides (gitignored)
`aitasks/metadata/board_config.json`	Project	No	Board column definitions
`aitasks/metadata/board_config.local.json`	User	Yes (Board)	User board settings (gitignored)
`aitasks/metadata/project_config.yaml`	Project	Yes (Project Config)	Shared workflow settings such as coauthor domain and build verification
`aitasks/metadata/models_claudecode.json`	Project	No	Claude Code model definitions
`aitasks/metadata/models_geminicli.json`	Project	No	Gemini CLI model definitions
`aitasks/metadata/models_codex.json`	Project	No	Codex CLI model definitions
`aitasks/metadata/models_opencode.json`	Project	No	OpenCode model definitions
`aitasks/metadata/profiles/*.yaml`	Project	Yes (Profiles)	Execution profiles (git-tracked)
`aitasks/metadata/profiles/local/*.yaml`	User	Yes (Profiles)	User execution profiles (gitignored)

Profile Schema

Execution profiles are YAML files with the following keys. All keys are optional – omitted keys cause the corresponding question to be asked interactively.

Settings

Mon, 01 Jan 0001 00:00:00 +0000

Launching

ait settings

The Settings TUI requires the shared Python virtual environment (installed by ait setup) with the textual and pyyaml packages.

Understanding the Layout

The Settings TUI organizes configuration into five tabs, each accessible via a keyboard shortcut displayed in the footer.

Agent Defaults (a)

The Agent Defaults tab shows which code agent and model is configured for each operation.

/aitask-revert

Mon, 01 Jan 0001 00:00:00 +0000

Revert changes associated with completed tasks — fully or partially. This skill analyzes a task’s commits, identifies affected areas, and creates a self-contained revert task with all the information needed to undo the changes. Use it when a feature adds unnecessary complexity, an experiment didn’t pan out, or you want to selectively undo parts of a completed task.

Usage:

/aitask-revert # Interactive: discover task to revert
/aitask-revert 42 # Direct: revert task t42
/aitask-revert t42 # Also accepted with t prefix

Note: Must be run from the project root directory. See Skills overview for details.

/aitask-create

Mon, 01 Jan 0001 00:00:00 +0000

Create a new task file with automatic numbering and proper metadata via interactive code agent prompts.

Usage:

/aitask-create

Note: Must be run from the project root directory. See Skills overview for details.

Step-by-Step

The skill guides you through task creation using interactive prompts:

Parent selection — Choose standalone or child of existing task
Task number — Auto-determined from active, archived, and compressed tasks
Metadata — Priority, effort, dependencies (with sibling dependency prompt for child tasks)
Task name — Free text with auto-sanitization
Definition — Iterative content collection with file reference insertion via Glob search
Create & commit — Writes task file with YAML frontmatter and commits to git

Batch Mode

For non-interactive task creation (e.g., scripting or automation), use the underlying script directly with --batch:

/aitask-wrap

Mon, 01 Jan 0001 00:00:00 +0000

Retroactively wraps uncommitted changes into the aitasks framework. When you’ve made changes outside the normal task flow — quick fixes, debugging improvements, config tweaks — this skill analyzes the diff, creates a task and plan file documenting the changes, commits everything with proper format, and archives it in one flow.

Usage:

/aitask-wrap

Note: Must be run from the project root directory. See Skills overview for details.

Step-by-Step

Detect changes — Scans for uncommitted changes (staged, unstaged, and untracked). Aborts if nothing to wrap
Select files — Choose to include all changes or select specific files
Analyze diff — Reads the full diff and determines: factual summary, probable intent, suggested issue type, task name, labels, priority, and effort. In Claude Code, also checks ~/.claude/plans/ for a recent internal plan that matches the changes and incorporates it into the plan file if found
Confirm analysis — Presents the analysis for review. Adjust task name, metadata, or descriptions before proceeding
Execute — After a final confirmation gate, runs everything without further prompts: creates task file → creates plan file → commits code changes → archives task and plan → pushes to remote
Summary — Displays the created task, plan, commit hashes, and archive status
Satisfaction feedback — Optional prompt to record how well the wrap served your needs. Controlled by enableFeedbackQuestions; see Verified Scores

Key Capabilities

Auto-analysis — Reads the diff to infer intent, suggest an issue type (feature, bug, refactor, etc.), and generate task/plan descriptions
Metadata suggestions — Suggests priority, effort, and labels based on diff size and file paths. All suggestions are adjustable before execution
Single confirmation gate — All user interaction happens before Step 5. Once confirmed, everything executes sequentially without interruption
All-in-one execution — Task creation, plan creation, code commit, archival, and push happen in a single automated sequence
Edge case handling — Handles large diffs (>2000 lines) with truncation warnings, mixed staged/unstaged changes, and untracked files

When to Use

Scenario	Skill
Changes already made, need to document retroactively	`/aitask-wrap`
Planning work before starting implementation	`/aitask-create`
Want to explore the codebase first, then create a task	`/aitask-explore`

Use /aitask-wrap when you’ve accumulated uncommitted changes that weren’t tracked through the normal task flow — quick fixes applied directly, debugging sessions that turned into real improvements, config or dependency changes made outside the framework, or pair programming sessions where changes accumulated without task tracking.

/aitask-stats

Mon, 01 Jan 0001 00:00:00 +0000

View task completion statistics via a code agent.

Usage:

/aitask-stats

Note: Must be run from the project root directory. See Skills overview for details.

Runs ./.aitask-scripts/aitask_stats.sh and displays the results. Provides the same statistics as ait stats, including:

Summary counts (7-day, 30-day, all-time)
Daily breakdown with optional task IDs
Day-of-week averages
Per-label weekly trends (4 weeks)
Label day-of-week breakdown (30 days)
Task type weekly trends
Label + issue type trends
Code agent weekly trends (last 4 weeks)
LLM model weekly trends (last 4 weeks)
Verified model score rankings per skill (pick, explain, batch-review) – see Verified Scores for how scores are accumulated
- All-providers aggregated view with per-provider breakdowns
- Time-windowed display (all-time, this month)

Supports all command-line options (-d, -v, --csv, -w). For interactive terminal charts (including code agent / LLM model histograms and verified score ranking bar charts per skill), run ait stats-tui or switch into it from any other aitasks TUI via the TUI switcher. For CSV export, provides guidance on opening the file in LibreOffice Calc with pivot tables and charts.

/aitask-explain

Mon, 01 Jan 0001 00:00:00 +0000

Explain files in the project by providing detailed analysis of their functionality, real usage examples from the codebase, and code evolution history traced through aitask and aiplan records. The unique value of this skill is answering not just “what does this code do” but “why does it exist and how did it get here” — by connecting code sections back to the tasks that motivated each change and the plan notes that document the reasoning.

/aitask-changelog

Mon, 01 Jan 0001 00:00:00 +0000

Generate a changelog entry by analyzing commits and archived plans since the last release. Orchestrates the ait changelog command with AI-powered summarization.

Usage:

/aitask-changelog

Note: Must be run from the project root directory. See Skills overview for details.

Step-by-Step

Gather release data — Runs ait changelog --gather to collect all tasks since the last release tag, with their issue types, plan files, commits, and implementation notes
Summarize plans — Reads each task’s archived plan file and generates concise user-facing summaries (what changed from the user’s perspective, not internal details)
Draft changelog entry — Groups summaries by issue type under ### Features, ### Bug Fixes, ### Improvements headings. Format: - **Task name** (tNN): summary
Version number — Reads VERSION file, calculates next patch/minor, asks user to select or enter custom version
Version validation — Ensures the selected version is strictly greater than the latest version in CHANGELOG.md (semver comparison)
Overlap detection — Checks if any gathered tasks already appear in the latest changelog section. If overlap found, offers: “New tasks only”, “Replace latest section”, or “Abort”
Review and finalize — Shows the complete formatted entry for approval. Options: “Write to CHANGELOG.md”, “Edit entry”, or “Abort”
Write and commit — Inserts the entry into CHANGELOG.md (after the # Changelog header) and commits

Key Features

User-facing summaries: focuses on what changed, not implementation details
Version validation prevents duplicate or regressive version numbers
Overlap detection handles incremental changelog updates when some tasks were already documented
Supports both new CHANGELOG.md creation and insertion into existing files

Workflows

For a full workflow guide covering the release pipeline, see Releases.

/aitask-review

Mon, 01 Jan 0001 00:00:00 +0000

Review code using configurable review guides, then create tasks from findings. This skill separates code quality review from implementation — first build something that works, then systematically review it for quality improvements.

Usage:

/aitask-review # Interactive: choose scope and review guides

Note: Must be run from the project root directory. See Skills overview for details.

Codex CLI note: When continuing from this skill into implementation, in Codex wrappers, after implementation, most of the times you will need to explicitly tell the agent to continue the workflow because request_user_input is only available in plan mode. Example prompts: Good, now finish the workflow or Good, now continue.

Stable on aitasks

/aitask-pick

Kanban Board

How-To Guides

How to Organize Tasks into Columns

How-To Guides

How to Navigate Files in the Tree

How to Navigate Code

How-To Guides

How Minimonitor Is Auto-Spawned

How-To Guides

How to Start the Monitor

Monitor

Minimonitor

/aitask-explore

Code Browser

How-To Guides

Mouse Support

Feature Reference

Keyboard Shortcuts

Board Navigation

Task Operations

Column Operations

Modal Navigation

Task Card Anatomy

Feature Reference

Keyboard Shortcuts

Application

History Screen

Label Filter Dialog

Sibling Picker Dialog

Code Viewer

Go-to-Line Dialog

Mouse Interactions

Annotation Data Pipeline

Feature Reference

Keyboard Shortcuts

Zone Navigation

Pane Interaction

Monitor Controls

/aitask-pr-import

/aitask-contribute

/aitask-contribution-review

/aitask-fold

Reference

Keyboard Shortcuts

Global

Within Tabs

Mouse Interactions

Tabs

Agent Defaults Operations

Configuration Files

Profile Schema

Settings

Launching

Understanding the Layout

Agent Defaults (a)

/aitask-revert

/aitask-create

Step-by-Step

Batch Mode

/aitask-wrap

Step-by-Step

Key Capabilities

When to Use

/aitask-stats

/aitask-explain

/aitask-changelog

Step-by-Step

Key Features

Workflows

/aitask-review