Skip to main content
ClaudeWave
Skill2.9k repo starsupdated 17d ago

find-code-tasks

The find-code-tasks skill scans a repository for `.code-task.md` files and displays their status, dates, and metadata in various formats including table, JSON, or summary counts. Use it to review pending work at the start of a session, track task progress across the backlog, filter tasks by status, or export task data for reporting purposes.

Install in Claude Code
Copy
git clone --depth 1 https://github.com/mikeyobrien/ralph-orchestrator /tmp/find-code-tasks && cp -r /tmp/find-code-tasks/.claude/skills/find-code-tasks ~/.claude/skills/find-code-tasks
Then start a new Claude Code session; the skill loads automatically.

SKILL.md

# 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 tasks
  - `in_progress` - Show only in-progress tasks
  - `completed` - Show only completed tasks
  - (none) - Show all tasks

- **format** (optional, default: "table"): Output format
  - `table` - Human-readable table with status symbols
  - `json` - JSON array for programmatic use
  - `summary` - Counts by status only

- **tasks_dir** (optional, default: ".ralph/tasks/"): Directory to search for tasks

## Usage Examples

```bash
# 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:

```bash
# 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.md` to 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-generator` to 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

```json
[
  {"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:

```yaml
---
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`
code-assistSkill

Guides implementation of code tasks using test-driven development in an Explore, Plan, Code, Commit workflow. Acts as a Technical Implementation Partner and TDD Coach — following existing patterns, avoiding over-engineering, and producing idiomatic, modern code.

ralph-e2e-verifierSubagent

Use this agent when you need to run the Ralph orchestrator end-to-end test suite, analyze diagnostic outputs, and generate comprehensive reports of findings. This includes validating backend connectivity, orchestration loop behavior, event parsing, hat collections, memory systems, and error handling. Invoke this agent after making changes to core orchestration logic, before releases, or when debugging integration issues.\\n\\nExamples:\\n\\n<example>\\nContext: User has made changes to the event parsing logic and wants to verify nothing is broken.\\nuser: \"I just modified the event parsing in ralph-core, can you verify everything still works?\"\\nassistant: \"I'll use the ralph-e2e-verifier agent to run the full E2E test suite and analyze the results.\"\\n<Task tool invocation to launch ralph-e2e-verifier>\\n</example>\\n\\n<example>\\nContext: User is preparing a release and needs validation.\\nuser: \"We're preparing to release v0.5.0, please run the E2E tests\"\\nassistant: \"I'll launch the ralph-e2e-verifier agent to run comprehensive E2E tests across all backends and generate a release readiness report.\"\\n<Task tool invocation to launch ralph-e2e-verifier>\\n</example>\\n\\n<example>\\nContext: User notices orchestration issues and wants diagnostics analyzed.\\nuser: \"Ralph seems to be selecting the wrong hats, can you investigate?\"\\nassistant: \"I'll use the ralph-e2e-verifier agent to run E2E tests with diagnostics enabled and analyze the hat selection decisions.\"\\n<Task tool invocation to launch ralph-e2e-verifier>\\n</example>

ralph-loop-runnerSubagent

Use this agent when you need to execute a Ralph orchestration loop end-to-end and verify its completion. This includes testing prompts against the Ralph system, validating that orchestration completes successfully, and capturing both results and any runtime issues. Examples:\\n\\n<example>\\nContext: User wants to test if a prompt works correctly with Ralph orchestration.\\nuser: \"Test if Ralph can handle the prompt 'create a hello world function'\"\\nassistant: \"I'll use the ralph-loop-runner agent to execute this prompt through Ralph and verify completion.\"\\n<Task tool call to ralph-loop-runner agent>\\n</example>\\n\\n<example>\\nContext: User is debugging why a Ralph run failed.\\nuser: \"Run this spec through Ralph and tell me what went wrong\"\\nassistant: \"Let me use the ralph-loop-runner agent to execute this and capture any runtime problems.\"\\n<Task tool call to ralph-loop-runner agent>\\n</example>\\n\\n<example>\\nContext: User wants to validate Ralph behavior after code changes.\\nuser: \"I just modified the event parser, can you run a test loop?\"\\nassistant: \"I'll use the ralph-loop-runner agent to run a complete orchestration loop and verify the changes work correctly.\"\\n<Task tool call to ralph-loop-runner agent>\\n</example>

code-task-generatorSkill

Generates structured .code-task.md files from descriptions or PDD implementation plans. Auto-detects input type, creates properly formatted tasks with Given-When-Then acceptance criteria.

evaluate-presetsSkill

Use when testing Ralph's hat collection presets, validating preset configurations, or auditing the preset library for bugs and UX issues.

pddSkill

Transforms a rough idea into a detailed design document with implementation plan. Follows Prompt-Driven Development — iterative requirements clarification, research, design, and planning.

playwriterSkill

Browser automation via Playwriter (remorses) using persistent Chrome sessions and the full Playwright Page API.

pr-demoSkill

Use when creating animated demos (GIFs) for pull requests or documentation. Covers terminal recording with asciinema and conversion to GIF/SVG for GitHub embedding.