一键导入
yarstack-create-todo
Create a committed Markdown todo in ~/.create-todo from a todo, task, follow-up, $create-todo request, or current conversation context.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Create a committed Markdown todo in ~/.create-todo from a todo, task, follow-up, $create-todo request, or current conversation context.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Report all repository changes that entered a target branch during one required date or period, grouped by product change and written as plain English for a broad audience. Use for daily, weekly, date-range, or relative-period change summaries rather than explaining one known diff.
Create one concise evidence-linked product journey record for one actor pursuing one goal. Use when product behavior needs traceable ownership, acceptance, telemetry, or service-flow documentation for a current decision or delivery gate.
Review documentation for drift caused by the current code or configuration change. Use to identify concrete inaccuracies and, when authorized, repair only directly affected documentation.
Audit or improve general repository documentation against implemented behavior. Use for deliberate README or documentation-quality work not owned by a more specific documentation skill.
Review English technical prose without modifying it. Use for plain-English feedback on comments, docstrings, documentation, commit or pull request text, issues, reports, runbooks, logs, errors, command help, and other human-readable technical writing rather than factual or marketing review.
Audit or, when authorized, rewrite persuasive product claims against shipped-product evidence. Use for landing pages, marketing-heavy READMEs, feature or pricing pages, comparisons, and calls to action.
| name | yarstack-create-todo |
| description | Create a committed Markdown todo in ~/.create-todo from a todo, task, follow-up, $create-todo request, or current conversation context. |
Create one durable Markdown todo from the user's request and current conversation context.
# Title, then a concise freeform body.Source: https://github.com/owner/repo.Confirm the action and acceptance criteria are clear.
Generate the todo title and body.
Capture the user's current working directory, then run the bundled script from this skill directory with that source directory:
source_dir="$PWD"
skill_dir="<directory containing this SKILL.md>"
"$skill_dir/create-todo.sh" --cwd "$source_dir" "<title>"
The script prints two lines:
Write the Markdown content to the returned file path.
Format the todo:
bunx prettier --write "$todo_file"
If bunx is unavailable, use:
npx prettier --write "$todo_file"
If formatting fails, stop before committing.
Commit only the new todo file in ~/.create-todo:
todo_root="$HOME/.create-todo"
todo_rel="${todo_file#"$todo_root"/}"
git -C "$todo_root" add -- "$todo_rel"
git -C "$todo_root" commit -m "todo: <short title>" -- "$todo_rel"
Do not stage or commit any other files. If the commit fails, surface git's error.
If ~/.create-todo has an origin remote, push main:
git -C "$HOME/.create-todo" push origin main
If no origin exists, report that the todo was committed locally and push was skipped. If push fails, report that the todo was created and committed, then surface the push error.
create-todo.sh owns deterministic file creation and first-run todo-store setup:
~/.create-todomain when neededREADME.md and .gitignore as initialize todo store when the todo store has no commits--cwd git origin, git root, or folder name~/.create-todo/<project_slug>/<YYYY-MM-DD>-<title_slug>-<HHMMSS>-<4hex>.md