issues
Skill2 starsChanged 9 days agoMITView on GitHub
Use when opening an issue or changing its title or description. Produces an actionable problem record for a decider with no project context.
21 other projects use a version of this.
Adopted by
Most recently taken up by
- pedrohcgs/claude-code-my-workflowtheir own version, first seen Nov 8, 2026
- halilural/imprimaturtheir own version, first seen Nov 8, 2026
- davidvornholt/mail-mcpword for word, first seen Nov 5, 2026
- ecosyste-ms/claude-plugintheir own version, first seen Oct 25, 2026
- dotBunny/Claudettetheir own version, first seen Oct 25, 2026
- fslzrr/skillstheir own version, first seen Oct 20, 2026
Used with
Projects with it also use prd, architecture and 1 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.
GitHubSkillprd
Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.
Also in 6 projects that use this
AnthropicSkillarchitecture
Create or evaluate an architecture decision record (ADR). Use when choosing between technologies (e.g., Kafka vs SQS), documenting a design decision with trade-offs and consequences, reviewing a system design proposal, or designing a new component from requirements and constraints.
Also in 3 projects that use this
SentrySkillcommit
Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.
Also in 5 projects that use this
Other versions21 projects use a version of this.
Word for word · 1
- davidvornholt/mail-mcp★ 2100% same
Edited · 0
None found.
Wrote their own version · 20
- pedrohcgs/claude-code-my-workflow★ 1.7ksame name
- martinus/unordered_dense★ 1.5ksame name
- bjcoombs/ai-native-toolkit★ 32same name
- 0xrafasec/ai-workflow★ 9same name
- rafagomes/ai-workflow★ 9same name
- dotBunny/Claudette★ 7same name
- Magnus-Gille/claude-skills★ 5same name
- ecosyste-ms/claude-plugin★ 3same name
- ecosyste-ms/skills★ 3same name
- devskale/skale-skills★ 2same name
10 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 repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ci-pipelinesSkill
- databaseSkill
- declarative-infraSkill
- frontend-designSkill
- nextjsSkill
- prsSkill
- review-fixSkill
- reviewSkill
- screenshots-in-prsSkill
- secrets-and-configSkill
- standards-syncSkill
- ux-uiSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 19 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 18
Put the support for the problem under ## Evidence: observations, reproduction steps, measurements, code references, or sources, without …
- Very specific: line 20
Add ## Decision only when work can't start until someone makes a choice.
“Common” is measured: kept by at least 6 in 10 of the 19 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
Issues
Whoever decides on an issue or picks it up, often an agent, reads it later without your context. Give it a plain-language title that names the problem or the desired outcome, and open the description with exactly these two paragraphs:
**Problem.** The current behavior or missing ability, who or what it affects, and its concrete cost or risk.
**Outcome.** The observable result or decision that closes the issue.The outcome says when the issue is done, not how. Name an implementation only when one is already decided, because whoever picks up the issue will treat a suggested approach as settled.
Put the support for the problem under ## Evidence: observations, reproduction steps, measurements, code references, or sources, without restating the opening.
Add ## Decision only when work can't start until someone makes a choice.
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.