file-issue
Skill3 starsChanged 6 days agoApache-2.0View on GitHub
Turn the owner's idea, bug or request into a complete GitHub issue (never their words verbatim), asking only about missing requirements; files when told. Use for "add to GitHub", "file an issue", "track this", or a rough feature description.
14 other projects use a version of this.
Adopted by
Most recently taken up by
- Termherd/termherdtheir own version, first seen Nov 8, 2026
- razbakov/skillstheir own version, first seen Nov 8, 2026
- enes-alatas/spooltheir own version, first seen Nov 8, 2026
- Sma1lboy/rovetheir own version, first seen Nov 6, 2026
- rome-os/rometheir own version, first seen Oct 21, 2026
- ultimatile/development-skillstheir own version, first seen Oct 20, 2026
Used with
Projects with it also use review-pr.
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.
DockerSkillreview-pr
Review one or more incoming Docker documentation pull requests as a maintainer. Independently validate technical claims, assess editorial fit and information architecture, choose a verdict, and draft exact inline or PR-wide feedback behind a confirmation gate. Use for requests such as "review PR 123", "is this PR correct?", "does this information belong here?", "validate this PR", or "help review backlog PRs". Do not use to maintain or fix a PR you own; use maintain-pr for that.
Also in 4 projects that use this
Other versions14 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 14
- marin-community/marin★ 4.1ksame name
- rilldata/rill★ 3ksame name
- levy-street/world-of-claudecraft★ 2.3ksame name
- rome-os/rome★ 894same name
- open-thoughts/OpenThoughts-Agent★ 309same name
- Sma1lboy/rove★ 184same name
- enes-alatas/spool★ 48same name
- mlz11/ClaudeNotifier★ 36same name
- razbakov/skills★ 4same name
- bhagyamudgal/skills★ 2same name
4 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.
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 13 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 25
Ask only when the request leaves a material requirement unresolved, then fold the answer into the draft.
- Very specific: line 31
If the owner already asked to file, add to GitHub, or track the issue, publish the completed draft with gh issue create without asking …
“Common” is measured: kept by at least 6 in 10 of the 13 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
File an issue
The owner's raw ask is input, not the issue. The GitHub issue must stand alone for whoever implements it months later.
1. Rewrite, don't transcribe
Draft the issue with:
- Title: imperative, specific, under about 70 characters, no internal jargon.
- What and why: the user-visible behavior and the reason it matters.
- Acceptance criteria: verifiable bullets, each checkable by a walkthrough or test.
- Out of scope: what this issue deliberately does not change.
2. Clarify material gaps
Ask only when the request leaves a material requirement unresolved, then fold the answer into the draft. Routine wording and title choices do not require another approval round.
3. File when told
If the owner already asked to file, add to GitHub, or track the issue, publish
the completed draft with gh issue create without asking again. A request to
draft an issue does not authorize publishing it.
Report the URL. Never start implementing as part of this flow.
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.