How do I install the Close Ticket skill?

Run npx skillmds@latest add reebeecka/close-ticket in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Close Ticket safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Close Ticket?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Close Ticket free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Close Ticket?

Reebeecka (@reebeecka) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Close Ticket by reebeecka — Agent Skill

Name: Close Ticket
Author: Reebeecka

File contents

close-ticket

Prove the ticket is done, then open a PR and update the ticket. Do not build more scope. Merge is the user's decision unless they explicitly ask to merge.

API calls: ../ticket-platform/PLATFORM.md. Backend = last-used, else ask.

After a successful close-ticket run, write a SESSION_TREE in chat (see the session-tree skill).

No ticket

If there is no GitHub issue / Jira key: say so. A PR is allowed. It cannot be "closed" against a ticket. Do not invent an id.

Fail-closed

Any required item red → no PR, unless the user explicitly overrides. Overrides and remaining gaps go in the PR body.

One ticket per PR

Always. Other work leaves the branch first (revert, stash, or a new ticket + later PR).

Checklist

Run in order. Label every acceptance line Observed / Inferred / Assumed. Code inspection is not Observed.

Identify the ticket. Read its acceptance and out of scope.
Diff vs ticket. git diff / git status mapped to acceptance. Files that do not belong → stop; split a new ticket or revert before PR.
Acceptance. Each box, with evidence (command, URL, what appeared). Unproven = fail.
Tests. Run the relevant suite. New logic needs at least one test that would fail without the change. No harness → this item is fail (say so); do not silent-pass. User may override.
Lint / types. Clean, or user-approved exception.
Dual-pass review (if this workspace has a review skill, use it on the diff; always do both passes):
- Confirmation: what is correct and working
- Adversarial: what is missing, what breaks on edges. If the adversarial pass finds nothing, look again.
UI / integration if the ticket touches UI or a user flow: exercise the path the ticket names, plus other surfaces that read the same state. If a browser is not available, this item is not Observed — state the gap and wait for the gate (user may override, same as fail-closed).
Commits on the branch reference the ticket (#n or PROJ-123). Fix messages before opening the PR.
Gate. Show the filled checklist (pass/fail per item). Wait for yes, unless the user already said "öppna PR".
PR against main or develop. Body links the ticket. GitHub: Closes #n (closes on merge, not before). Jira: key in title and body.
CI. If the repo has CI, wait for gh pr checks. If not, skip.
Ticket comment with what changed + PR URL.
Jira transition: waiting-on-review (see platform file). Never Done. GitHub issue stays open until merge.

Gate output

Ticket: <id>
Acceptance: pass/fail (each line + Observed/Inferred/Assumed)
Tests: pass/fail (command + result)
Lint: pass/fail
Review: confirmation / adversarial
UI: pass/fail/gap
Scope extra: none / STOP
PR: <url or blocked>
Ticket update: <done or n/a>
Overrides: <none or list>

---name: close-ticketdescription: Prove a ticket is done (acceptance evidence, tests, dual-pass review, PR, ticket update). Use when the user says a ticket is done, asks to open a PR, or the agent is about to claim the work is complete.---# close-ticketProve the ticket is done, then open a PR and update the ticket. Do not build more scope. Merge is the user's decision unless they explicitly ask to merge.API calls: [../ticket-platform/PLATFORM.md](../ticket-platform/PLATFORM.md). Backend = last-used, else ask.After a successful close-ticket run, write a `SESSION_TREE` in chat (see the session-tree skill).## No ticketIf there is no GitHub issue / Jira key: say so. A PR is allowed. It cannot be "closed" against a ticket. Do not invent an id.## Fail-closedAny required item red → no PR, unless the user explicitly overrides. Overrides and remaining gaps go in the PR body.## One ticket per PRAlways. Other work leaves the branch first (revert, stash, or a new ticket + later PR).## ChecklistRun in order. Label every acceptance line **Observed** / **Inferred** / **Assumed**. Code inspection is not Observed.1. **Identify** the ticket. Read its acceptance and out of scope.2. **Diff vs ticket.** `git diff` / `git status` mapped to acceptance. Files that do not belong → stop; split a new ticket or revert before PR.3. **Acceptance.** Each box, with evidence (command, URL, what appeared). Unproven = fail.4. **Tests.** Run the relevant suite. New logic needs at least one test that would fail without the change. No harness → this item is fail (say so); do not silent-pass. User may override.5. **Lint / types.** Clean, or user-approved exception.6. **Dual-pass review** (if this workspace has a `review` skill, use it on the diff; always do both passes): - Confirmation: what is correct and working - Adversarial: what is missing, what breaks on edges. If the adversarial pass finds nothing, look again.7. **UI / integration** if the ticket touches UI or a user flow: exercise the path the ticket names, plus other surfaces that read the same state. If a browser is not available, this item is not Observed — state the gap and wait for the gate (user may override, same as fail-closed).8. **Commits** on the branch reference the ticket (`#n` or `PROJ-123`). Fix messages before opening the PR.9. **Gate.** Show the filled checklist (pass/fail per item). Wait for yes, unless the user already said "öppna PR".10. **PR** against `main` or `develop`. Body links the ticket. GitHub: `Closes #n` (closes on merge, not before). Jira: key in title and body.11. **CI.** If the repo has CI, wait for `gh pr checks`. If not, skip.12. **Ticket comment** with what changed + PR URL.13. **Jira transition:** waiting-on-review (see platform file). **Never Done.** GitHub issue stays open until merge.## Gate output```Ticket: <id>Acceptance: pass/fail (each line + Observed/Inferred/Assumed)Tests: pass/fail (command + result)Lint: pass/failReview: confirmation / adversarialUI: pass/fail/gapScope extra: none / STOPPR: <url or blocked>Ticket update: <done or n/a>Overrides: <none or list>```

Frequently asked questions

Close Ticket