Lists all code tasks in the repository with their status, dates, and metadata. Useful for getting an overview of pending work or finding specific tasks.
This skill finds and displays all code tasks (.code-task.md files) in the repository, showing their frontmatter status and metadata. Use it to get a quick overview of pending work, find tasks by status, or check the state of the task backlog.
filter (optional): Filter tasks by status
pending - Show only pending tasksin_progress - Show only in-progress taskscompleted - Show only completed tasksformat (optional, default: "table"): Output format
table - Human-readable table with status symbolsjson - JSON array for programmatic usesummary - Counts by status onlytasks_dir (optional, default: ".ralph/tasks/"): Directory to search for tasks
# Show all tasks in table format
/find-code-tasks
# Show only pending tasks
/find-code-tasks filter:pending
# Get JSON output for tooling
/find-code-tasks format:json
# Quick summary of task counts
/find-code-tasks format:summary
# Search custom directory
/find-code-tasks tasks_dir:tools/
The script is colocated with this skill at .claude/skills/find-code-tasks/task-status.sh.
Execute it with appropriate arguments:
# Default: table format, all tasks
.claude/skills/find-code-tasks/task-status.sh
# With filter
.claude/skills/find-code-tasks/task-status.sh --pending
.claude/skills/find-code-tasks/task-status.sh --in_progress
.claude/skills/find-code-tasks/task-status.sh --completed
# With format
.claude/skills/find-code-tasks/task-status.sh --json
.claude/skills/find-code-tasks/task-status.sh --summary
# Custom tasks directory
TASKS_DIR=tools/ .claude/skills/find-code-tasks/task-status.sh
Display the output to the user. For table format, the output includes:
| Symbol | Status | |--------|--------| | ○ | pending | | ● | in_progress | | ✓ | completed | | ■ | blocked |
Based on the results, suggest relevant actions:
/code-assist .ralph/tasks/<task-name>.code-task.md to start a task"/code-task-generator to create new tasks"TASKS STATUS
════════════════════════════════════════════════════════════════
TASK STATUS DATE
────────────────────────────────────────────────────────────────
○ add-task-frontmatter-tracking pending 2025-01-15
○ enhance-headless-tool-output pending -
● fix-ctrl-c-freeze in_progress 2025-01-14
✓ replay-backend completed 2025-01-13
────────────────────────────────────────────────────────────────
Total: 4 tasks
Task Summary
────────────
○ Pending: 10
● In Progress: 2
✓ Completed: 5
────────────
Total: 17
[
{"task": "add-task-frontmatter-tracking", "status": "pending", "created": "2025-01-15", "started": null, "completed": null},
{"task": "fix-ctrl-c-freeze", "status": "in_progress", "created": "2025-01-14", "started": "2025-01-14", "completed": null}
]
Tasks with frontmatter tracking have this structure:
---
status: pending | in_progress | completed | blocked
created: YYYY-MM-DD # Date task was created
started: YYYY-MM-DD # Date work began (null if not started)
completed: YYYY-MM-DD # Date work finished (null if not done)
---
Tasks without frontmatter are shown as pending with null dates.
If no tasks are displayed:
ls .ralph/tasks/.code-task.md/find-code-tasks tasks_dir:./If the task-status.sh script is not found:
ls .claude/skills/find-code-tasks/task-status.shchmod +x .claude/skills/find-code-tasks/task-status.shIf dates show as - for tasks with frontmatter:
--- on line 1status, created, started, completedSearch for places (restaurants, cafes, etc.) via Google Places API proxy on localhost.
OpenProse VM skill pack. Activate on any `prose` command, .prose files, or OpenProse mentions; orchestrates multi-agent workflows.
Use CodexBar CLI local cost usage to summarize per-model usage for Codex or Claude, including the current (most recent) model or a full model breakdown. Trigger when asked for model-level usage/cost data from codexbar, or when you need a scriptable per-model summary from codexbar cost JSON.
Control Philips Hue lights and scenes via the OpenHue CLI.
Start voice calls via the OpenClaw voice-call plugin.
Best practices for using the oracle CLI (prompt + file bundling, engines, sessions, and file attachment patterns).
Category:developer