菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| 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.
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, completedGenerates 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.
Use when testing Ralph's hat collection presets, validating preset configurations, or auditing the preset library for bugs and UX issues.
Introspect, explain, and improve Ralph Orchestrator using its published llms.txt doc map. Use this skill whenever the user asks questions about Ralph's behavior, wants to understand how a Ralph internal works (event loop, hats, memories, tasks, backends, presets), debug an unfamiliar failure mode, or propose a code change to the ralph-orchestrator repo. The skill teaches the agent to discover authoritative answers from the live docs via llms.txt before guessing, and to scope improvements through the published architecture rather than the local checkout alone.
Run, monitor, resume, merge, and debug Ralph loops. Use this skill whenever the user asks to operate `ralph run` or `ralph loops`, inspect loop state, recover suspended loops, analyze diagnostics, or unblock merge queue issues.
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.
Transforms a rough idea into a detailed design document with implementation plan. Follows Prompt-Driven Development — iterative requirements clarification, research, design, and planning.