agentleFS
Sign inStart free
felirangelpfelirangelp/harness-driven-dev/.claude/skills/close-issue/SKILL.md

close-issue

Skill15 starsChanged 6 months agoMITView on GitHub

Close a Linear issue with evidence — runs 3 gates (tests, CI, acceptance criteria) before closing

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. MillenniumDawn/Millennium-Dawn★ 158same name
    2. dmzoneill/skills★ 2same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do NOT close the issue

    line 32
  2. Distinctive:

    NEVER close an issue if a gate fails.

    line 37
  3. Distinctive:

    NEVER use workarounds to bypass gates.

    line 38
  4. Distinctive:

    NEVER close issues manually in Linear — always use this skill.

    line 39

≈ “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 Issue

Close Linear issue $ARGUMENTS with mechanical verification.

Steps

  1. Run the harness gate script:
    bash scripts/close_issue.sh $0
    This runs 3 gates:
    • Gate 1: Tests passing? (npm test)
    • Gate 2: CI green? (gh run list)
    • Gate 3: Acceptance criteria all checked? (Linear API)
  2. If ALL gates pass: The script automatically:
    • Posts evidence comment to the Linear issue
    • Moves issue to "Done"
    • Report: Issue $0 closed with evidence.
  3. If ANY gate fails:
    • Report which gate failed and why
    • Do NOT close the issue
    • Suggest what the user needs to fix

Rules

  • NEVER close an issue if a gate fails.
  • NEVER use workarounds to bypass gates.
  • NEVER close issues manually in Linear — always use this skill.
  • The user must fix the root cause, then run /close-issue again.

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