菜单
Turn the remaining todos of the current conversation into a GitHub project of task-spec issues wired with native blocked-by dependencies.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/rome-os/rome --skill todos-to-github-project命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Triage and answer automated code-review findings on a PR without growing its scope. Use when the user asks to "handle / address / respond to review feedback", "go through the bot comments", or after the RomeOS review bots (zoolsher, Jessie-QingYu) post findings on a PR. Classify every finding before writing any code — most findings deserve a reply, not a diff. NOT for requesting a review (that is /code-review) and NOT for reviewing someone else's PR.
Hold an interactive session to create or revise an ideal-state doc, or to slice it into approved repository milestones.
Autonomously compute the gap between an ideal-state doc and the codebase, then file the next work issues — or a loop-complete or loop-needs-discussion report.
正在显示 SKILL.md
| name | todos-to-github-project |
| description | Turn the remaining todos of the current conversation into a GitHub project of task-spec issues wired with native blocked-by dependencies. |
| disable-model-invocation | true |
Goal end-state: every remaining todo of the conversation is one task-spec issue, the issues sit in one GitHub project, every dependency is a blocked-by edge on GitHub, and each in-scope issue carries ready-for-agent.
The issue format — title, body sections, the ready-for-agent bar — is defined in docs/authoring/github-issues.md. Prose in titles and bodies follows docs/authoring/WRITING.md. This skill covers what to file, in which order, and with which gh calls.
gh issue list --search "<keywords>". If an existing issue already tracks it, drop the todo from the set.ready-for-agent. An issue still waiting on a user decision files without the label.The draft stays out of chat. Ask for the go-ahead in one line — the project title and the issue count — and write nothing to GitHub before the user gives it. Present issue titles or bodies only when the user asks to see them.
If gh label list does not show ready-for-agent, create it with gh label create ready-for-agent.
Resolve the repo and owner: gh repo view --json nameWithOwner.
Create the project: gh project create --owner <owner> --title "<title>".
Link the project to the repo so it shows up under the repo's Projects tab: gh project link <project-number> --owner <owner> --repo <owner>/<repo>.
Create the issues in dependency order, blockers first, so every Blocked by line names a real issue number: gh issue create --title "<title>" --body "<body>" --label ready-for-agent.
Add each in-scope issue to the project: gh project item-add <project-number> --owner <owner> --url <issue-url>.
Mirror every edge into GitHub's native relation. The issue_id is the blocking issue's numeric REST id (gh api repos/<owner>/<repo>/issues/<number> --jq .id), not its issue number:
gh api -X POST repos/<owner>/<repo>/issues/<blocked-number>/dependencies/blocked_by -F issue_id=<blocking-id>
gh repo view --json projectsV2. The new project must appear in the list.gh project item-list <project-number> --owner <owner>. The count must match the in-scope set.gh api repos/<owner>/<repo>/issues/<number>/dependencies/blocked_by. Every drafted edge must appear.