implement
Skill21 starsChanged 41 days agoMITView on GitHub
Implement a Linear issue
191 other projects use a version of this.
Adopted by
Most recently taken up by
- revisit-studies/studytheir own version, first seen Nov 9, 2026
- dz114879/skillstheir own version, first seen Nov 8, 2026
- Dimon94/dveritytheir own version, first seen Nov 8, 2026
- Dimon94/skillstheir own version, first seen Nov 8, 2026
- The-Vibe-Company/quivrtheir own version, first seen Nov 8, 2026
- miklschmidt/archboardtheir own version, first seen Nov 8, 2026
Used with
Projects with it also use setup-ts-deep-modules, ask-matt 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.
liufeng1976Skillsetup-ts-deep-modules
Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.
Also in 43 projects that use this
GoogleSkillask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
Also in 91 projects that use this
RoentekSkillloop-me
Grill me about specs for the workflows I want to build, within this workspace.
Also in 50 projects that use this
AWSSkillto-questionnaire
Turn a decision you can't fully answer into a questionnaire for someone else to fill in.
Also in 88 projects that use this
ryotaroh180105Skillclaude-handoff
Hand the current conversation off to a fresh background agent that picks up the work immediately.
Also in 42 projects that use this
- GoogleSkill
to-spec
Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
Also in 168 projects that use this
- +3 more from google
Other versions191 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 191
- mattpocock/skills★ 309ksame name
- QuivrHQ/quivr★ 40ksame name
- The-Vibe-Company/quivr★ 40ksame name
- foambubble/foam★ 17ksame name
- formbricks/formbricks★ 13ksame name
- ArcReel/ArcReel★ 6.3ksame name
- vinvcn/mattpocock-skills-zh-CN★ 5.5ksame name
- fallow-rs/fallow★ 5.3ksame name
- withcoral/coral★ 4.9ksame name
- bestofjs/bestofjs★ 3.1ksame name
181 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 repository5 other files it gives its agents.
- address-pr-reviewSkill
- interviewSkill
- tell-grokbotSkill
- unslop-frSkill
- unslopSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 171 edited versions we read keep these.
4
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 12
If no issue is given, ask the user for one.
- Very specific: line 19
Create a new branch from the up-to-date default branch.
- Distinctive: line 23
If the issue has sub-issues, ask which ones are in scope.
- Distinctive: line 26
If the issue came with an implementation plan, even partial (in its original description or in a comment), start from it instead of …
- Distinctive: line 30
If the issue is large in scope, you can break it down and delegate to sub-agents or use a workflow.
“Common” is measured: kept by at least 6 in 10 of the 171 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
Linear issue (e.g. ENG-123, or a linear.app/... issue URL):
$ARGUMENTS
If no issue is given, ask the user for one.
Whenever this skill says to ask the user, ask one question at a time (with the AskUserQuestion tool in Claude Code).
- Fetch the Linear issue using the Linear MCP, including its comments, parent issue, sub-issues, attachments, and linked documents or designs.
- Fetch related issues and the Linear project (description, documents, milestones) if applicable.
- Move the issue to the team's started status (usually "In Progress").
- Create a new branch from the up-to-date default branch. Name it after the branch name Linear suggests for the issue (
gitBranchName), or else the lowercase issue identifier (e.g.eng-123). If the working tree has uncommitted changes, ask the user what to do first. - Explore the code related to the issue, so that you don't ask questions the code already answers.
- Clarify the specs:
- Make no assumptions: keep asking the user about anything the Linear issue or the code doesn't answer, until you have no questions left.
- If the issue has sub-issues, ask which ones are in scope.
- Once the specs are clear, update the Linear issue description with the detailed specs and move on to the next step.
- Design the high-level architecture. The goal of this step is to catch a design going down the wrong path early.
- If the issue came with an implementation plan, even partial (in its original description or in a comment), start from it instead of designing from scratch: only go through what it leaves open or unclear, and what the clarified specs changed.
- For small changes, state the approach in one sentence and move on.
- Otherwise, go through the design with the user one decision at a time, instead of presenting the whole design at once. The user must approve any significant change to the existing architecture before you write code.
- Implement the issue. Make sure to write tests. When relevant, test in a sandbox or staging environment. If you are stuck, ask the user for help or clarification.
- If the issue is large in scope, you can break it down and delegate to sub-agents or use a workflow.
- Open a pull request. In the description, reference the issue with
Fixes ENG-123so that Linear closes it on merge, orPart of ENG-123if the PR only covers part of the issue. - Monitor the PR for build failures or review comments.
- When you are done, give the user the PR link and flag anything that may need their action: decisions you made on your own, deviations from the specs, what you could not test, and the Linear issues you created. Keep it short and leave out anything that needs no action.
All along this process, if you find issues in the product that are not related to your work (or tooling that could help you), record them in new Linear issues. Search for duplicates first, create them in the same team, and link them to the current issue as related.
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.