code-assist
Guides implementation of code tasks using test-driven development in an Explore, Plan, Code, Commit workflow. Acts as a Technical Implementation Partner and…
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.
$ npx -y skills add mikeyobrien/ralph-orchestrator --skill find-code-tasks --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/find-code-tasksContext preview
The summary Claude sees to decide when to auto-load this skill.
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.
name: find-code-tasks description: 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. type: anthropic-skill version: "1.0" metadata: internal: true
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.
# 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:
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 tasksTask 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:
If the task-status.sh script is not found:
If dates show as `-` for tasks with frontmatter:
A hat-based orchestration framework that keeps AI agents in a loop until the task is done. "Me fail English? That's unpossible!" - Ralph Wiggum
Repo: mikeyobrien/ralph-orchestrator
Guides implementation of code tasks using test-driven development in an Explore, Plan, Code, Commit workflow. Acts as a Technical Implementation Partner and…
Generates structured .code-task.md files from descriptions or PDD implementation plans. Auto-detects input type, creates properly formatted tasks with…
Use when testing Ralph's hat collection presets, validating preset configurations, or auditing the preset library for bugs and UX issues.
Transforms a rough idea into a detailed design document with implementation plan. Follows Prompt-Driven Development — iterative requirements clarification,…
Browser automation via Playwriter (remorses) using persistent Chrome sessions and the full Playwright Page API.
Use when creating animated demos (GIFs) for pull requests or documentation. Covers terminal recording with asciinema and conversion to GIF/SVG for GitHub…