菜单
File a terse GitHub issue to track a task on any repo. Use when the user says "/todo", "this needs to be done", "file a todo", "track this", "make an issue for this", or points at work worth remembering later.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | todo |
| description | File a terse GitHub issue to track a task on any repo. Use when the user says "/todo", "this needs to be done", "file a todo", "track this", "make an issue for this", or points at work worth remembering later. |
| user-invocable | true |
| disable-model-invocation | false |
A todo is a title, not a document. Turn "this needs to be done" into a GitHub issue that reads like a note from a sharp engineer. The failure mode is verbosity. Every rule below exists to prevent it.
The title is the todo. Imperative, specific, names the object and the change. Under 70 characters, no trailing period.
Good: Add backoff retry to S3 uploader
Good: Pin tokio to 1.40 in workspace Cargo.toml
Bad: Improve upload reliability (names no change)
Bad: Fix issue where uploads sometimes fail due to transient errors (rambling)
The body is empty by default. Add a line only when the title cannot carry it. Three line types exist, all optional, one line each:
Done: transient 5xx retries 3x with jitter, hard failures still surface
Where: src/upload/s3.rs
Ref: #142
A genuinely multi-step task gets a checklist instead, 3 to 6 items, each one line:
- [ ] Wrap put_object in retry loop, max 4 attempts
- [ ] Retry only 5xx and timeouts, never 4xx
- [ ] Test: 503 twice then 200 still succeeds
Hard rules:
"Have Jace do this" means assign Jace. Resolve the name to a GitHub login:
gh api repos/<owner>/<repo>/assignees --jq '.[].login'.--assignee @me.Pass it as --assignee <login> on create. If GitHub rejects the assignment (not a collaborator), add one body line instead: cc @<login>. Assignment never adds any other text to the issue.
In order:
owner/repo in the request: use it.~/Documents/GitHub/<name> and read its origin remote, else match against gh repo list --json name --limit 100.gh repo view --json nameWithOwner.gh issue list --repo <repo> --state open --search "<keywords>"
If an open issue already covers it, reply with that issue's URL and stop. Do not file a duplicate.
gh issue create --repo <repo> --title "<title>" --body "<body, or empty string>" [--assignee <login>]
One line per issue: the URL. Nothing else.
Get the most out of Claude Fable 5 — the smartest generally available model, priced and positioned like it. Fable is the architect, not the workhorse: it plans, dictates tasks, evaluates, and verifies, while execution delegates down to GPT-5.6 Sol (headless codex), Sonnet 5, or Haiku 4.5 — Opus 4.8 when the work needs Agent-tool mechanics — unless the work is hard or high-stakes or the user asks for Fable by name. Use when the user says "/fable", "use fable", "use sol", "should this run on fable", asks which model should do a task, or questions model routing and cost. Always active when the session model is Fable 5 or when spawning subagents or workflows from a Fable session; also applies in reverse — summoning a Fable subagent from a cheaper session for work that deserves it.
Conversational style. Kill AI reply patterns. No filler openers, hedge stacks, recap closers, sycophancy, formatting theater, or jargon. One strong line first, depth on request. Always on. The plugin's SessionStart hook injects this into every session; follow it for every reply to a human.
Legacy instructions for delegating work to GLM, a sunset model that runs headless inside Claude Code. Use only when the user explicitly says "/glm", "ask glm", "have glm build/do this", "let glm", or "delegate to glm"; never invoke it automatically for frontend/UI or other work.
The canonical, opinionated technology stack for any new project — what to reach for, in what order, and what to never touch. Use this whenever a new project starts or a stack decision comes up: scaffolding an app, prototype, dashboard, landing page, or design system, or picking a framework, UI library, database, ORM, auth, hosting, animation lib, or any dependency. Triggers include "new project", "start building", "scaffold", "spin up a site/app", "what should I use for", "which framework/library/database", "set up auth", "add a backend", "where do I deploy", "build a prototype". Always active when choosing or installing technology.
Delegate research, code review, or collaborative sparring to Codex CLI. Use when user says "/codex", "ask codex", "delegate to codex", "have codex look into", "codex review", "spar with codex", "go back and forth with codex", "use codex to pressure-test", or when a problem is non-trivial enough that a second model's perspective would meaningfully improve the answer.
Search Claude Code chat history (past sessions, threads, conversations) via the `clog` CLI. Use when the user asks to find an old session, recall what was discussed about something, look up which branch or repo a chat was on, count sessions by topic, or pull message text from an archived conversation. Triggers include "find that session", "search my chats", "what did we discuss about X", "look up the conversation where", "which chat covered X", "claude history", "past sessions", "remember when we worked on", "find sessions about".