find-code-tasks
Lists and filters task status from markdown files within your repository.
Install
mkdir -p .claude/skills/find-code-tasks && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/5936" && unzip -o skill.zip -d .claude/skills/find-code-tasks && rm skill.zipInstalls to .claude/skills/find-code-tasks
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
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.Key capabilities
- →Scan repository for task files
- →Filter tasks by status
- →Generate task status tables
- →Export task data as JSON
- →Summarize task backlog
How it works
It scans a designated directory for files with the .code-task.md extension and parses their YAML frontmatter to report status and metadata.
Inputs & outputs
When to use find-code-tasks
- →Reviewing the development task backlog
- →Checking task status before starting work
- →Exporting task progress for reporting
About this skill
Find Code Tasks
Overview
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.
When to Use
- Starting a work session to see what tasks are available
- Checking status of tasks before/after running code-assist
- Finding tasks by status (pending, in_progress, completed)
- Getting a summary of task backlog
- Exporting task data for reporting
Parameters
-
filter (optional): Filter tasks by status
pending- Show only pending tasksin_progress- Show only in-progress taskscompleted- Show only completed tasks- (none) - Show all tasks
-
format (optional, default: "table"): Output format
table- Human-readable table with status symbolsjson- JSON array for programmatic usesummary- Counts by status only
-
tasks_dir (optional, default: ".ralph/tasks/"): Directory to search for tasks
Usage Examples
# 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/
Steps
1. Run Task Status Script
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
2. Present Results
Display the output to the user. For table format, the output includes:
| Symbol | Status |
|---|---|
| ○ | pending |
| ● | in_progress |
| ✓ | completed |
| ■ | blocked |
3. Suggest Next Actions
Based on the results, suggest relevant actions:
- If there are pending tasks: "Run
/code-assist .ralph/tasks/<task-name>.code-task.mdto start a task" - If there are in_progress tasks: "There are tasks already in progress - consider completing those first"
- If all tasks are completed: "All tasks are done! Use
/code-task-generatorto create new tasks"
Output Examples
Table Format (default)
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
Summary Format
Task Summary
────────────
○ Pending: 10
● In Progress: 2
✓ Completed: 5
────────────
Total: 17
JSON Format
[
{"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}
]
Frontmatter Schema
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.
Integration with Other Skills
- code-task-generator: Creates new tasks with frontmatter
- code-assist: Updates task status when starting/completing work
- ralph-code-assist: Runs tasks through Ralph orchestrator
Troubleshooting
No Tasks Found
If no tasks are displayed:
- Verify the tasks directory exists:
ls .ralph/tasks/ - Check file extension is
.code-task.md - Try specifying directory:
/find-code-tasks tasks_dir:./
Script Not Found
If the task-status.sh script is not found:
- Ensure you're in the repository root
- Check the script exists:
ls .claude/skills/find-code-tasks/task-status.sh - Make it executable:
chmod +x .claude/skills/find-code-tasks/task-status.sh
Frontmatter Not Parsed
If dates show as - for tasks with frontmatter:
- Ensure frontmatter starts with
---on line 1 - Check YAML syntax is valid
- Verify field names match:
status,created,started,completed
When not to use it
- →When tasks are not stored in .code-task.md files
Limitations
- →Only tracks files with .code-task.md extension
- →Requires valid YAML frontmatter for status tracking
How it compares
It provides a standardized way to query task status across a repository compared to manually searching or tracking files.
Compared to similar skills
find-code-tasks side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| find-code-tasks (this skill) | 1 | 5mo | Review | Beginner |
| task-management | 16 | 5mo | No flags | Beginner |
| compact | 4 | 6mo | Review | Beginner |
| daily | 1 | 5mo | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by mikeyobrien
View all by mikeyobrien →You might also like
task-management
anthropics
Simple task management using a shared TASKS.md file. Reference this when the user asks about their tasks, wants to add/complete tasks, or needs help tracking commitments.
compact
catlog22
Compact current session memory into structured text for session recovery. Supports custom descriptions and tagging.
daily
ballred
Create daily notes and manage morning, midday, and evening routines. Structure daily planning, task review, and end-of-day reflection. Use for daily productivity routines or when asked to create today's note.
markdown-task-manager
ioniks
Use when managing tasks, the system is a Kanban task manager based on local Markdown files (`kanban.md` and `archive.md`). It follows a strict format compatible with the task-manager.html web application.
feature-pipeline
notedit
Execute implementation tasks from design documents using markdown checkboxes. Use when (1) implementing features from feature-analyzer output, (2) resuming interrupted work, (3) batch executing tasks. Triggers on 'start implementation', 'run tasks', 'resume'.
create-issue
not-elm
>