create-issue
Skill2 starsChanged 38 days agoMITView on GitHub
Write issues that stand on their own, on any tracker. Use to file a bug, task or decision, turn findings into issues, or plan a change as a tracking issue with ordered child issues.
63 other projects use a version of this.
Adopted by
Most recently taken up by
- neko3cs/skillstheir own version, first seen Nov 8, 2026
- dsifry/metaswarmtheir own version, first seen Nov 8, 2026
- alexander-kastil/copilot-harnesstheir own version, first seen Nov 8, 2026
- nateslabach/skillstheir own version, first seen Nov 8, 2026
- blamechris/chroxytheir own version, first seen Nov 8, 2026
- javierbrea/eslint-plugin-boundariestheir own version, first seen Nov 2, 2026
Used with
Projects with it also use native-nostalgia-stack, software-engineering-excellence and 8 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
frostneySkillnative-nostalgia-stack
Applies the user's FreePascal toolchain and its build, formatting, hook, and test contracts while leaving project-specific mechanics local. Use when scaffolding or working in a FreePascal project that follows this toolchain.
Also in 3 projects that use this
- frostneySkill
software-engineering-excellence
Applies the user's engineering standards during substantial technical work: preserve scope, use current evidence, delegate independent parts, and complete authorized outcomes. Use during substantial implementation, debugging, refactoring, or multi-part delivery work.
Also in 3 projects that use this
withpiperSkillroadmap-review
Audit roadmap health — issues, dependency order, spec coverage, doc freshness. Use when speccing a new initiative. Use when /phase-plan output looks suspicious. Use before /roadmap-create reruns.
Also in 3 projects that use this
GoogleSkillimplement-issue
Implement a Site Kit GitHub issue end-to-end from its implementation brief. Use when the user asks to implement, build, or work on a GitHub issue / feature by number (e.g. "implement issue #12345", "build the feature in issue 12345", "follow the implementation brief for #12345") in the google/site-kit-wp repo.
Also in 6 projects that use this
Microsoft AzureSkillcreate-release
Use when creating a new ASO release, including pre-checks, release notes generation, draft GitHub release creation, documentation updates, and ROADMAP changes.
Also in 4 projects that use this
MicrosoftSkillupdate-pr
Update the pull request for the current session. Use when the user wants to push new changes to an existing PR.
Also in 3 projects that use this
Other versions63 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 63
- penpot/penpot★ 62ksame name
- videojs/video.js★ 40ksame name
- yugabyte/yugabyte-db★ 11ksame name
- antiwork/gumroad★ 10ksame name
- gitkraken/vscode-gitlens★ 10ksame name
- camunda/camunda★ 4.4ksame name
- robustmq/robustmq★ 1.9ksame name
- aws-powertools/powertools-lambda-typescript★ 1.8ksame name
- classroomio/classroomio★ 1.7ksame name
- tikv/pd★ 1.2ksame name
53 more not listed
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 repository18 other files it gives its agents.
- AGENTS.mdAGENTS.md
- atlassianSkill
- auditSkill
- code-qualitySkill
- commit-expertSkill
- create-prSkill
- debugSkill
- defineSkill
- deliverSkill
- final-reviewSkill
- gherkinSkill
- githubSkill
- handoffSkill
- plainSkill
- second-opinionSkill
- senior-technical-writerSkill
- testingSkill
- triageSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 53 edited versions we read keep these.
1
Distinctive
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
- Distinctive: line 40
Search for a duplicate, open or closed.
“Common” is measured: kept by at least 6 in 10 of the 53 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Create issue
The draft format, commands and creation script come from the skill for the project's tracker, such as github. Issue kinds, labels and milestones come from the project.
Rules
- Size issues as Size says. Several issues that reach one goal in order are a program.
- Carry the intent, not the plan: why the change matters, the design it reaches, and how to tell it is done. The steps belong to whoever builds it.
- Lead with the problem in this repository and its evidence.
- Link code at a commit, never a branch.
- How another project handles the same thing may be cited as fact, never as the reason. Do not frame the work as copying it, or as an audit's output.
- A bug states the correct behaviour as a Gherkin scenario, which fails today. Its acceptance is the regression test that implements it.
- The issue stands alone: no local or gitignored paths, no internal ids such as audit keys.
References
| Task | Read |
| Plan a change as a tracking issue with ordered child issues | references/programs.md |
Size
The user picks how much one issue holds. Ask once, before drafting more than a few issues; the default is pr.
| Size | One issue is | Ships as |
finding | One defect or one change, the smallest that can ship alone | One pull request |
pr | What one reviewer takes as one pull request: one cause, category or seam | One pull request |
outcome | One outcome a reviewer can check, such as a theme's goal | One pull request or a stack |
At every size, group with judgement: keep together what cannot ship apart, and split an issue whose title needs two outcomes.
Flow
- Search for a duplicate, open or closed.
- Draft each issue in the tracker skill's format, using the project's closest kind: a bug, a task, or a decision for a question a maintainer must answer first.
- Validate and show the user what would be created. Create only after they approve, then follow the tracker skill's board.
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
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.