菜单
This skill should be used when the user asks to "review past work", "過去の作業を確認", "what was done", "TODO履歴", or wants past task and TODO history from previous sessions reviewed.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Auto-activate CCS CLI delegation for deterministic tasks. Parses user input, auto-selects optimal profile (glm/kimi/custom) from ~/.ccs/config.json, enhances prompts with context, executes via `ccs {profile} -p "task"` or `ccs {profile}:continue`, and reports results. Triggers on "use ccs [task]" patterns, typo/test/refactor keywords. Excludes complex architecture, security-critical code, performance optimization, breaking changes.
Internal project-context placement and consistency reference used by context refactoring and verification workflows.
This skill should be used when the user asks to "audit project standards", "check standards compliance", "devkit audit", "find standards violations", "are we following devkit standards", "what's not following standards", "compliance report", "規約チェック", "スタンダード監査", or "規約違反を探して". It actively scans code and reports violations. Do NOT use for project scaffolding (use init-project), single-CLI-tool checks (use cli-compliance), or looking up what the standards are (use standards).
This skill should be used when the user asks to "set up a project", "choose a tech stack", "establish coding standards", "configure linting", "set up tests", "pick a framework", "review code quality", "set up logging", "configure observability", "choose an ORM", "set up auth", "set up Storybook", "write stories", "visual testing", "CSF", "coverage threshold", or discusses any technology choices for a TypeScript project. Also use when starting a new project, setting up CI/CD, choosing between tools (oxlint vs ESLint, pnpm vs npm), configuring environment variables, or when any other devkit skill needs to reference project conventions. This is the central reference for all devkit technology decisions and coding principles.
Review whether the current code satisfies a GitHub issue, then update the issue status to match. Use when the user asks to 'review an issue', 'check if an issue is done', 'is this issue resolved', 'update issue status', 'issueの対応状況を確認', 'issueが完了しているかレビュー', or 'issueのステータスを更新'.
This skill should be used when the user asks to 'create a skill', 'add a new skill', 'make a skill', 'scaffold a skill', 'new skill', 'スキル化して', 'スキルを作成', 'スキルを追加', or wants to create a new Claude Code skill for a plugin or project. Provides a guided workflow with automated scaffolding, validation, and dynamic context injection.
| name | task-history |
| description | This skill should be used when the user asks to "review past work", "過去の作業を確認", "what was done", "TODO履歴", or wants past task and TODO history from previous sessions reviewed. |
| allowed-tools | Bash(${CLAUDE_PLUGIN_ROOT}/skills/task-history/query.ts *), Read |
Display task and TODO history persisted by the task-history PostToolUse hook.
$ARGUMENTS
Run the query tool to retrieve history:
${CLAUDE_PLUGIN_ROOT}/skills/task-history/query.ts [options]
--recent N — Show last N events
--session ID — Filter by session ID
--status STATUS — Filter by status (pending, in_progress, completed)
--since DATE — Show events since ISO date
# Recent 50 events (default)
${CLAUDE_PLUGIN_ROOT}/skills/task-history/query.ts
# Only completed tasks
${CLAUDE_PLUGIN_ROOT}/skills/task-history/query.ts --status completed
# Events from today
${CLAUDE_PLUGIN_ROOT}/skills/task-history/query.ts --since 2026-03-24