agentleFS
Sign inStart free
kyto64kyto64/aidd-template-scale/.agents/skills/close-ticket/SKILL.md

close-ticket

Skill0 starsChanged 2 months agoMITView on GitHub

After PR merge: verify issue state, update docs, add closing comment if needed.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If no merged PR and issue still open → stop and tell user to merge first.

    line 17
  2. Very specific:

    Update docs/ if the issue required documentation changes not yet done.

    line 21
  3. Very specific:

    Update docs/_inventory.md when SSOT boundaries change.

    line 22
  4. Distinctive:

    If issue is closed (via merge): add a short comment summarizing what shipped and doc paths updated.

    line 26
  5. Very specific:

    If issue is still open after merge (missing Fixes # keyword): ask user to close manually or fix PR template for next time.

    line 27

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Close ticket workflow

Issue number: $ARGUMENTS

Step 1: Verify

  1. gh issue view $ARGUMENTS — check state (open/closed)
  2. Find merged PR with Fixes #$ARGUMENTS via gh pr list --state merged --search "$ARGUMENTS"
  3. If no merged PR and issue still open → stop and tell user to merge first.

Step 2: Docs

  1. Update docs/ if the issue required documentation changes not yet done.
  2. Update docs/_inventory.md when SSOT boundaries change.

Step 3: Issue comment

  1. If issue is closed (via merge): add a short comment summarizing what shipped and doc paths updated.
  2. If issue is still open after merge (missing Fixes # keyword): ask user to close manually or fix PR template for next time.

Step 4: Cleanup (optional)

Remind user to remove worktree per git-worktree.md when done.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free