メニュー
Use when the user is done working on a Linear ticket and wants to wrap up - creates PR, runs code review, merges, updates the ticket status, and cleans up the worktree
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/dkuehlwein/nova --skill end-ticketコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
SOC 職業分類に基づく
Use when the user wants to create a Linear ticket, issue, user story, or task - interviews the user adaptively, formats as a user story with test plan, and creates it via Linear MCP after confirmation
Use when the user wants to start working on a Linear ticket - fetches ticket details, creates a git worktree with a properly named branch, and launches a subagent in the worktree with full ticket context and the right workflow skill
| name | end-ticket |
| description | Use when the user is done working on a Linear ticket and wants to wrap up - creates PR, runs code review, merges, updates the ticket status, and cleans up the worktree |
Wrap up work on a Linear ticket through a fixed pipeline: verify tests, commit, create PR, run code review, merge, update the ticket, and clean up the worktree. The mirror of start-ticket.
Accept an optional ticket reference from the user. It can be:
NOV-123https://linear.app/team/issue/NOV-123/...If not provided, extract the ticket ID from the current branch name. The expected pattern is {prefix}/{TICKET-ID}-{slug} (e.g., fix/NOV-123-login-crash yields NOV-123).
Before anything else, check the current branch:
main or master, stop with error: "end-ticket is for feature branches, not main/master."Fetch ticket details using the Linear MCP get_issue tool. If the ticket can't be found, tell the user and stop.
Show a summary before proceeding:
Ticket: NOV-123 - Fix login crash on empty email
Status: In Progress
Branch: fix/NOV-123-login-crash-on-empty-email
Ask the user: "Tests were run recently -- skip or re-run?"
cd backend && uv run pytest ../tests
Run git status to check for uncommitted changes.
fix: Resolve login crash on empty email (NOV-123)). Follow the standard commit process from CLAUDE.md -- show the diff, draft a message, and commit.Check if a PR already exists for this branch:
gh pr list --head <branch-name> --json number,url
git push -u origin <branch-name>gh pr create:
After the PR exists (whether new or existing):
update_issue with the links parameter.update_issue.Invoke the code-review:code-review skill on the PR using the Skill tool.
Evaluate the results:
Unit tests ran on the branch (Phase 2). Now merge locally and run integration tests on main before pushing.
Note the PR number from Phase 4 -- you'll need it for the commit message.
Switch to main and pull latest:
git checkout main
git pull origin main
Squash merge the branch:
git merge --squash <branch-name>
If this fails (conflicts): git merge --abort, switch back to the branch, and tell the user to resolve manually. Stop here.
Remove the implementation plan (if one exists):
git rm docs/plans/{TICKET-ID}-*.md
Plan files are ephemeral — they served their purpose during development and should not land on main. If no plan file exists, skip this step (the glob will simply match nothing).
Run integration tests on main:
cd backend && uv run pytest ../tests/integration -v
git reset --hard origin/main
git checkout <branch-name>
Commit the squash merge with both the PR number and ticket ID:
git commit -m "fix: Resolve login crash (NOV-123) (#42)"
Use conventional commit format. The PR number goes at the end in parentheses.
Push main:
git push origin main
This automatically closes the PR on GitHub.
Delete the remote branch:
git push origin --delete <branch-name>
Update the ticket: set the Linear ticket status to "Done" using update_issue.
Clean up the local branch:
git branch -d <branch-name>
Check for worktree: run git worktree list and check whether the original working directory was a git worktree.
git worktree remove <worktree-path>Report completion:
Ticket NOV-123 done. PR #42 merged to main. Worktree cleaned up.
main or master): stop immediately with an error message.git merge --abort, switch back to the branch, tell user to resolve.git reset --hard origin/main, switch back to branch, show failures.gh pr list --head <branch> before creating a new PR. Duplicate PRs cause confusion.git reset --hard origin/main before switching back to the branch.cd out of the worktree directory before it can be removed.