菜单
Review an asset at version 0.0.0 against the repo conventions and graduate it to 0.1.0 once it passes. Use when the user wants to review a template, graduate a template, mark a template stable, bump from 0.0.0, or close a template-review issue.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Walk through creating a new asset in todoist-playbook (CSV template, prompt template, or bundle). Use when the user wants to add a new template, add a new prompt, add a new bundle, scaffold a Todoist template, or create a starter kit. Bundles meta.yml / bundle.yml / template.csv / prompt.md stubs.
Branch, commit, push, and open a PR using the repo conventions and gh CLI. Use when the user says open a PR, create a pull request, push a branch, ship this, or commit and push.
Run the validate-templates checks locally on Windows before pushing. Use when the user wants to validate templates locally, run validation, check meta.yml, verify CSV header, or reproduce CI validation failures.
| name | review-unreviewed-asset |
| description | Review an asset at version 0.0.0 against the repo conventions and graduate it to 0.1.0 once it passes. Use when the user wants to review a template, graduate a template, mark a template stable, bump from 0.0.0, or close a template-review issue. |
Graduate a CSV template, prompt template, or bundle from version: 0.0.0 (unreviewed) to 0.1.0 (reviewed and stable).
sync-template-review-issues.yml) needs closing0.0.0 long enough to assessConfirm the slug, asset type, and current version: in the metadata file. If version: is not 0.0.0, stop — this skill is only for first review.
Delegate the full review to the template-reviewer custom agent (read-only, returns a single review summary). For a manual review, walk the relevant scoped instructions:
Run the SEO Accessibility Agent as a mandatory secondary pass for all review outcomes, including create/update/delete recommendations.
The asset must:
validate-templates.ymlREADME.md that is accurate, complete, and includes the right kind of guidance for the asset typecategory: (re-use an existing value where one fits)Fix everything the review flags. If a finding requires a behavioural change to the asset, that is in scope; if it requires a behavioural change to validation, raise it as a separate issue.
Hand-edit the metadata file:
version: 0.1.0
Note: this is the ONE legitimate hand-bump. After 0.1.0, bump-template-version.yml takes over patch bumps automatically on merged PRs — do not hand-edit version: again.
Use a chore/ branch with a work item ID (e.g. chore/1234-review-{slug}) and a Conventional Commits message such as:
chore: graduate {slug} to version 0.1.0
In the PR body, link the corresponding template-review issue and summarise the review findings. sync-template-review-issues.yml will close the review issue once the change is merged.