Development
Skill
/task-history
Reads and displays task execution history from crew-history.json with filtering by type, agent, cost, and configurable limits.
Claude Code
$ npx -y skills add d3x293/code-crew --skill task-history --agent claude-code
Codex
$ npx skills add d3x293/code-crew --skill task-history -a codex -y
Cursor
$ npx skills add d3x293/code-crew --skill task-history -a cursor -y
Gemini CLI
$ npx skills add d3x293/code-crew --skill task-history -a gemini-cli -y
GitHub Copilot
$ npx skills add d3x293/code-crew --skill task-history -a github-copilot -y
OpenCode
$ npx skills add d3x293/code-crew --skill task-history -a opencode -y
Windsurf
$ npx skills add d3x293/code-crew --skill task-history -a windsurf -y
SKILL.md
task-history.SKILL.mdname: task-history
description: Reads and displays task execution history from crew-history.json with filtering by type, agent, cost, and configurable limits.
Task History - Execution History Viewer
Displays past task executions with filtering and cost analysis.
When to Activate
- User runs `/crew history [flags]`
Prerequisites
- `.claude/crew-history.json` must exist (created after first task execution)
- If missing: display "No history yet. Run /crew task to start."
Process
Step 1: Read History
Read `.claude/crew-history.json` — this is a JSON array of task entries (see execution-orchestrator for schema).
Step 2: Apply Filters
| Flag | Filter Logic | |------|-------------| | `--type <type>` | Keep only entries where `type` matches (bug-fix, feature, refactor, docs, test, security, devops, review, performance) | | `--agent <name>` | Keep only entries where `agents[]` contains an agent with matching `name` | | `--limit <n>` | Show last N entries (default: 10) |
Filters stack: `--type bug-fix --agent debugger` shows bug-fixes that involved the debugger.
Step 3: Display Results
**Display format**:
Task History ({count} tasks shown, {total} total):
# | Timestamp | Type | Complexity | Agents | Mode | Status
1 | 2026-04-04 12:00 | bug-fix | moderate | debugger, senior-dev | full | SUCCESS
2 | 2026-04-04 11:30 | docs | trivial | doc-writer | lite | SUCCESS
3 | 2026-04-04 10:15 | feature | complex | vp-eng, senior-dev, test | full | SUCCESSStep 4: Summary Stats
After the table, show:
{count} tasks | Top: {type}({n}), {agent}({n}) | {percent}% successRead more
name: task-history description: Reads and displays task execution history from crew-history.json with filtering by type, agent, cost, and configurable limits.
Task History - Execution History Viewer
Displays past task executions with filtering and cost analysis.
When to Activate
- User runs `/crew history [flags]`
Prerequisites
- `.claude/crew-history.json` must exist (created after first task execution)
- If missing: display "No history yet. Run /crew task to start."
Process
Step 1: Read History
Read `.claude/crew-history.json` — this is a JSON array of task entries (see execution-orchestrator for schema).
Step 2: Apply Filters
| Flag | Filter Logic | |------|-------------| | `--type <type>` | Keep only entries where `type` matches (bug-fix, feature, refactor, docs, test, security, devops, review, performance) | | `--agent <name>` | Keep only entries where `agents[]` contains an agent with matching `name` | | `--limit <n>` | Show last N entries (default: 10) |
Filters stack: `--type bug-fix --agent debugger` shows bug-fixes that involved the debugger.
Step 3: Display Results
**Display format**:
Task History ({count} tasks shown, {total} total):
# | Timestamp | Type | Complexity | Agents | Mode | Status
1 | 2026-04-04 12:00 | bug-fix | moderate | debugger, senior-dev | full | SUCCESS
2 | 2026-04-04 11:30 | docs | trivial | doc-writer | lite | SUCCESS
3 | 2026-04-04 10:15 | feature | complex | vp-eng, senior-dev, test | full | SUCCESSStep 4: Summary Stats
After the table, show:
{count} tasks | Top: {type}({n}), {agent}({n}) | {percent}% success Stats
13
Stars
2
Forks
Quiet
Maintenance
MIT
License
Last commit
Created
Ships withcodecrew
A virtual dev crew for Claude Code — 11 specialized AI agents that decompose, implement, review, and ship your tasks. Instead of one AI doing everything, CodeCrew breaks work into subtasks and routes each to the right specialist on the right model.
1312 skills11 agents
Stars on GitHub
Momentum
- stars in total
- 13
Other skills on codecrew.
More skills from other plugins.
Auto-invoked
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
@obraInstall Skillask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
@mattpocockInstall SkillAuto-invoked
Questions about task-history.
- Which coding agents can use task-history?
- task-history installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.