linear-issue
Skill839 starsChanged 51 days agoApache-2.0View on GitHub
This skill should be used when the user asks to "create a linear issue", "add a linear issue", "track this in linear", "open a linear ticket", "log this in linear", "create a ticket", or mentions creating an issue for tracking work in Linear.
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 5 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Create Linear issues pre-configured with Todo status, assigned to the current user.
- Very specific: line 30
Use the AIPerf team. Do not call list_teams or ask the user.
- Distinctive: line 34
If the context (current task, error, file, conversation) makes a suitable title obvious, propose one that satisfies the constraints above.
- Distinctive: line 37
Always show the proposed title and wait for the user to confirm or revise before proceeding.
- Distinctive: line 50
Ask the user: "Do you want to add this to a Linear project?"
- Very specific: line 52
If yes: call mcp__linear__list_projects with the team from Step 1, present the list, then call mcp__linear__save_issue with id set to the …
- Distinctive: line 55
If no or no response: skip.
- Very specific: line 61
Ask the user: "Do you want to check out the branch <gitBranchName>?"
- Very specific: line 63
If yes: run git checkout -b <gitBranchName>.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Linear Issue Creator
Create Linear issues pre-configured with Todo status, assigned to the current user.
Title Constraints
Linear generates git branch names in the format username/TEAM-123-title-in-kebab-case.
With ~18 characters consumed by the username prefix and issue identifier, keep the title
50 characters or fewer and avoid characters that are illegal in git branch names
(~, ^, :, ?, *, [, \, spaces, ..).
Good titles (descriptive, short, branch-safe):
fix worker crash on empty responseadd latency percentile to reportupdate auth middleware for compliance
Bad titles:
Fix the worker service crash that happens when it receives an empty response— too longFix: worker crash!— contains special characters
Workflow
Step 1: Determine the team
Use the AIPerf team. Do not call list_teams or ask the user.
Step 2: Confirm the title
- If the context (current task, error, file, conversation) makes a suitable title obvious, propose one that satisfies the constraints above.
- Otherwise, ask the user for a short title.
- Always show the proposed title and wait for the user to confirm or revise before proceeding.
Step 3: Create the issue
Call mcp__linear__save_issue with:
title— confirmed title from Step 2team— team from Step 1assignee—"me"state—"Todo"
Step 4: Offer to add to a project
Ask the user: "Do you want to add this to a Linear project?"
- If yes: call
mcp__linear__list_projectswith the team from Step 1, present the list, then callmcp__linear__save_issuewithidset to the created issue identifier andprojectset to the chosen project name or ID. - If no or no response: skip.
Step 5: Offer to check out the branch
The save_issue response includes a gitBranchName field (e.g. dbermudez/aip-123-title).
Ask the user: "Do you want to check out the branch <gitBranchName>?"
- If yes: run
git checkout -b <gitBranchName>. - If no or no response: skip.
Step 6: Confirm
Report the created issue identifier (e.g. AIP-42) and title to the user.
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- phoenixmjay/claude-skills★ 0same name
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
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/python.mdcCursor rule
- aiperf-code-reviewSkill
- aiperf-kube-runSkill
- aiperf-kube-setupSkill
- aiperf-kube-sweepSkill
- aiperf-kube-triageSkill
- aiperf-llm-ergonomics-reviewSkill
- bump-versionSkill
- cherry-pickSkill
- docs-to-fernSkill
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.