issue
Skill2 starsChanged 54 days agoMITView on GitHub
Creates or triages a GitHub, GitLab, or Jira issue with its type, labels, priority, and fields filled from real values. Use when asked to open, file, report, or triage an issue or bug, or to turn a finding into a ticket.
- Reads credentials
50 other projects use a version of this.
Adopted by
Most recently taken up by
- pch/rawmakasetheir own version, first seen Nov 8, 2026
- jmusick/skillstheir own version, first seen Nov 8, 2026
- dimsedra/skillstheir own version, first seen Nov 8, 2026
- fab-codes/agent-workflow-templatetheir own version, first seen Nov 8, 2026
- egregore-labs/egregoretheir own version, first seen Nov 6, 2026
- elastic/docs-buildertheir own version, first seen Nov 4, 2026
Used with
Projects with it also use commit, browse and 7 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.
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 19 projects that use this
CodeWithBehnamSkillbrowse
Fast headless browser for QA testing and site dogfooding. Navigate any URL, interact with elements, verify page state, diff before/after actions, take annotated screenshots, check responsive layouts, test forms and uploads, handle dialogs, and assert element states. ~100ms per command. Use when you need to test a feature, verify a deployment, dogfood a user flow, or file a bug with evidence.
Also in 3 projects that use this
Microsoft AzureSkilltest
Also in 7 projects that use this
- Microsoft AzureSkill
lint
Run all linting and spell checking for TypeScript and Rust code. Run this before committing to catch style issues, clippy warnings, and misspellings.
Also in 4 projects that use this
lukeleekrSkillscout
GitHub 레포 스카우터. 내 Claude Code + Codex App 환경을 분석하여 필요한 GitHub 레포를 자동 추천하거나, 키워드로 GitHub을 검색합니다. "scout", "스카우트", "깃헙 탐방", "레포 추천", "repo search" 등의 키워드에 반응합니다.
Also in 3 projects that use this
sunnyclinches44Skillexplain
Explains code using real-world analogies and ASCII diagrams
Also in 4 projects that use this
- +1 more from Azure
Other versions50 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 50
- remotion-dev/remotion★ 72ksame name
- tldraw/tldraw★ 51ksame name
- tokio-rs/toasty★ 3.3ksame name
- dataplat/dbatools★ 2.9ksame name
- pch/rawmakase★ 1.6ksame name
- aws/graph-explorer★ 490same name
- egregore-labs/egregore★ 293same name
- finos/git-proxy★ 263same name
- alamenai/terrae★ 245same name
- awslabs/loom★ 201same name
40 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
5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 48 edited versions we read keep these.
3
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
When it is unclear, use the ask skill: GitHub, GitLab, or Jira.
- Distinctive: line 22
Search with the host skill's duplicates row, or with JQL on Jira.
- Distinctive: line 34
Read the valid labels, types, and fields with the host skill, and never invent one.
- Very specific: line 46
Do not default either field to Medium, and do not raise Priority to jump a queue.
- Distinctive: line 51
Create or triage with the host skill's row, which sets body, type, labels, and fields in one call on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 48 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
Issue
File one issue that does one thing, with every field set from values the tracker actually has.
1. Pick the tracker
| Tracker | When | Commands and template |
| GitHub | A GitHub remote, and no project key in the branch | The github skill, with templates/github-bug.md or templates/github-feature.md |
| GitLab | A GitLab remote, and no project key in the branch | The gitlab skill, with the same two templates |
| Jira | The branch or AGENTS.md carries a key such as KEY-123 | templates/jira-*.md, plus references/jira.md |
When it is unclear, use the ask skill: GitHub, GitLab, or Jira. Do not guess.
2. Look for a duplicate
Search with the host skill's duplicates row, or with JQL on Jira. Comment on a match instead of opening a duplicate.
3. Write
Fill every placeholder in the matching template. The title is imperative, under 72 characters,
with no period. A bug needs the version, steps, expected, and actual result. A feature leads with
the problem. Split a mixed report into one issue per thing. Keep tokens, .env lines, and
internal hostnames out of the body, and say where the value lives instead.
4. Classify from real values
Read the valid labels, types, and fields with the host skill, and never invent one. When the repo has no issue types or project fields, put Priority and Effort in the body.
Set the type first: Bug for something that broke or contradicts its docs, Feature for new behavior someone asked for, Task for work with no user-visible change (CI, releases, agent files).
| Field | Pick |
| Priority | Urgent blocks a release or breaks the published package for everyone. High hits users today with no workaround. Medium hits users with a workaround. Low is a nice-to-have |
| Effort | Low is one file a reviewer reads in one sitting. Medium spans a few files or needs a test. High needs a design decision or touches a public API |
Do not default either field to Medium, and do not raise Priority to jump a queue. When the type,
Priority, or Effort stays ambiguous, use the ask skill.
5. Create
Create or triage with the host skill's row, which sets body, type, labels, and fields in one call on GitHub.
Output
One line: the issue URL, then type, labels, Priority, and Effort. For a draft or a triage that creates nothing: the title and body, then the create payload.
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.