issue
Skill0 starsChanged 4 months agoMITView on GitHub
Create Linear issues from plain language. Use whenever the user asks to create a ticket, issue, task, or bug in Linear — even if they just say "file a ticket for X" or "create an issue about Y". The user provides a natural language description; this skill handles title, team, priority, description, and all CLI syntax. MUST be invoked before ANY linear-cli issues create command.
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 branch, commit and 10 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.
MindgamesSkillbranch
Use when a user asks to create a new local git branch and start issue work (for example, "create branch" or "start working on issue XYZ"). Use this for issue-based branch naming in the `type/scope-short-description` pattern and for always syncing local `main` from `origin/main` before creating the new branch, creating the local tracking `main` branch first when needed.
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 19 projects that use this
vertz-devSkillbacklog
Manages deferred/blocked work items as GitHub Issues with labels and blocker tracking
Also in 3 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
- +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.
In this repository14 other files it gives its agents.
- atddSkill
- brainstormingSkill
- ghSkill
- grafanaSkill
- linearSkill
- matter-cliSkill
- obsidianSkill
- ponytailSkill
- skill-creatorSkill
- slack-cliSkill
- slack-styleSkill
- systematic-debuggingSkill
- test-driven-developmentSkill
- tuxedoSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 48 edited versions we read keep these.
2
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 69
If context from the current conversation is relevant (error messages, file paths, service names), incorporate it into the description
- Distinctive: line 74
Do not ask the user to confirm parameters unless the team or priority is genuinely ambiguous.
“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
Create Linear Issue from Plain Language
The user describes what they want in plain language. You handle everything else.
How It Works
- User says something like:
/linear-issue create a ticket for removing duplicate appsettings files - You parse the intent and generate:
- A concise title (imperative, under 80 chars)
- Team (default:
<team>for infra work, infer from context otherwise) - Priority (infer from urgency/impact, default: 4 for housekeeping, 3 for normal, 2 for bugs)
- State (default:
Backlog) - A well-structured markdown description with Problem, Proposed Change, and Notes sections
CLI Syntax Reminder
Title is a POSITIONAL argument. Not --title.
linear-cli issues create "The Title" \
--team "<team>" \
--priority 4 \
--state "Backlog" \
--description "$(cat <<'EOF'
## Problem
What's wrong or missing.
## Proposed Change
What to do about it.
## Notes
Additional context.
EOF
)"Team Selection
CRITICAL — ignore "<org>" as a team name. "<org>" is the company, not the infra team. The <org> team (<prefix>) exists in Linear but is NOT for infra/devops/k8s/terraform work. If the user types "<org> team" while the topic is infra-context, route to <team> instead and confirm only if ambiguous. Past mistake: created <prefix>-46 instead of <prefix>-355 — user explicitly forbade <org> team for infra tickets.
| Context | Team |
| Infrastructure, Terraform, Kubernetes, CI/CD, DevOps, MQTT, services, deployments | <team> |
| IT operations, internal tools, accounts | IT |
| Other / unclear | Ask the user |
Never use <org>/<prefix> for infra tickets, even if the user literally says "<org> team". Confirm or override to <team>.
See the linear-cli skill for full team name-to-key mapping.
Priority Selection
| Signal | Priority |
| Production down, blocking, urgent | 1 (urgent) |
| Bug, broken functionality, security | 2 (high) |
| Feature request, normal task | 3 (normal) |
| Housekeeping, refactor, cleanup, tech debt | 4 (low) |
Workflow
- Parse the user's plain language request
- If context from the current conversation is relevant (error messages, file paths, service names), incorporate it into the description
- Generate the
linear-cli issues createcommand - Run it
- Report the issue ID and URL
Do not ask the user to confirm parameters unless the team or priority is genuinely ambiguous. Just create the issue — the user can always update it later.
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.