implement
Skill19 starsChanged 22 days agoApache-2.0View on GitHub
Load a Linear Issue and execute the full workflow from branch creation to implementation, testing, commit, and PR creation
- Commits and pushes
192 other projects use a version of this.
Adopted by
Most recently taken up by
- lhotwll217/owner-operatortheir own version, first seen Nov 16, 2026
- chuckplayer/claude-agent-packtheir own version, first seen Nov 16, 2026
- philoserf/claude-code-configtheir own version, first seen Nov 15, 2026
- muxy-app/muxytheir own version, first seen Nov 15, 2026
- geoffbremner/skillstheir own version, first seen Nov 15, 2026
- SireJeff/k0ntexttheir own version, first seen Nov 15, 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
GoogleSkillto-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 versions192 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 192
- mattpocock/skills★ 325ksame name
- QuivrHQ/quivr★ 40ksame name
- The-Vibe-Company/quivr★ 40ksame name
- foambubble/foam★ 17ksame name
- formbricks/formbricks★ 13ksame name
- ArcReel/ArcReel★ 6.6ksame name
- vinvcn/mattpocock-skills-zh-CN★ 5.8ksame name
- fallow-rs/fallow★ 5.3ksame name
- withcoral/coral★ 4.9ksame name
- bestofjs/bestofjs★ 3.1ksame name
182 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.
- CLAUDE.mdCLAUDE.md
- autopilotSkill
- buildSkill
- code-reviewSkill
- implement-pluginSkill
- license-checkSkill
- orchestrateSkill
- pentest-proxySkill
- projectSkill
- prSkill
- review-gateSkill
- security-reviewSkill
- testSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 5 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 175 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Update Issue status: Update status to "In Progress"
- Distinctive: line 31
Commit: Commit in Conventional Commits format, as a separate commit after the Step 6 red commit (do not amend or squash them together)
- Very specific: line 38
Create PR with gh pr create
- Distinctive: line 39
Update Issue status: Update status to "In Review"
- Very specific: line 44
Read .claude/agents/design-reviewer.md and replace the placeholders before launching:
- Distinctive: line 94
If build or tests fail, fix the issues before re-running
- Very specific: line 98
If PR creation fails, guide the user to manually run /pr
- Distinctive: line 99
Before completing implementation, verify that the feature is accessible from the config file (no missing config struct, validation, or init …
“Common” is measured: kept by at least 6 in 10 of the 175 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
/implement
An end-to-end workflow skill for implementing a Linear Issue through to PR creation.
Arguments
/implement <Issue ID>— Implement the specified Issue (e.g.,/implement USK-12)
Steps
- Load Issue: Fetch Issue details with
mcp__linear-server__get_issue - Update Issue status: Update status to "In Progress"
- Create branch: Generate an appropriate branch name from the Issue
- feat:
feat/<id>-<short-desc> - fix:
fix/<id>-<short-desc> - other:
chore/<id>-<short-desc>
- feat:
- Design review (mandatory for any Issue that introduces a new public type, modifies an interface, or touches more than one package; skip for docstring-only / test-only / single-call-site fixes — note the skip reason in the user-facing plan): launch the design-reviewer agent. See "Design Review Invocation" below.
- Present plan to user: Issue summary, file actions (new / modified / untouched), key resolved decisions from the design review, the Test Plan (the failing tests that will be written first), deferred items, unresolved questions. Get user confirmation before implementing. For trivial Issues that skipped Step 4, present a one-paragraph plan that still names the failing test(s) to write first, or the TDD exemption that applies.
- Red — write failing tests first: Follow "TDD Workflow" Phase 1 in
.claude/agents/implementer.md(it is the single source for the rules and exemptions). Write the tests plus compile-only scaffolding, run them withmake test-pkg PKG=<pkg> RUN=<regexp>, confirm each fails on its assertion (not a compile error orno tests to run), and commit them alone astest(<scope>): add failing tests for <Issue ID>. Keep the--- FAIL:lines for the PR body. - Green, then refactor: Implement until the Phase 1 tests pass, without weakening any Phase 1 assertion (implementer.md Phase 2), then refactor.
- Verify:
- Auto-format with
gofmt -w . make lint(gofmt check + golangci-lint: govet / staticcheck / unused / ineffassign / gocyclo)make buildmake test
- Auto-format with
- Commit: Commit in Conventional Commits format, as a separate commit after the Step 6 red commit (do not amend or squash them together)
- Include
Refs: <Issue ID>in the commit message footer
- Include
- Push: Push to remote with
git push -u origin <branch-name> - Create PR:
- Review changes with
git diff main...HEAD - PR title in Conventional Commits format (e.g.,
feat(protocol): add HTTP handler) - PR body follows the template below
- Create PR with
gh pr create
- Review changes with
- Update Issue status: Update status to "In Review"
- Report results: Display implementation summary + PR URL
Design Review Invocation
Read .claude/agents/design-reviewer.md and replace the placeholders before launching:
| Placeholder | Value |
{{SCOPE_DESCRIPTION}} | Issue title + description + tentative file action list (new / modified) inferred from the Issue |
{{SPEC_REFERENCES}} | Paths to relevant spec/design docs (docs/rfc/envelope.md for data path; protocol-specific RFCs; docs/rfc/plugin-migration.md for plugin work). Cite specific sections, not whole files. |
{{PACKAGES_TO_SURVEY}} | Packages the new code creates, modifies, or depends on |
{{COMPLETED_CONTEXT}} | One-paragraph summary of relevant existing public surface this Issue will integrate with (types/functions, not the whole architecture) |
{{PRODUCT_IDENTITY}} | Read from .claude/skills/review-gate/SKILL.md Phase 1-4 "Product context" block — single source of truth |
{{PRINCIPLES}} | The MITM Implementation Principles from CLAUDE.md (the 6-item list). Quote verbatim. |
Launch:
Agent(
description="Design review: <Issue ID>",
subagent_type="general-purpose",
prompt=<composed prompt>
)Process the result:
- All resolved → fold the resolved decisions table into the Step 5 plan
- Unresolved items exist → present only the unresolved questions to the user in Step 5 with the agent's proposed answers and trade-offs. Do not ask the user about resolved questions.
- Fitness check FAIL → stop and report. Do not proceed to Step 5 until the scope is adjusted.
PR Body Template
## Summary
- <bulleted list of changes>
## Test plan
- [ ] Test items
## TDD evidence
- Red commit: <sha> (or: exempt — <reason>)
- Failing output at the red commit:--- FAIL: TestX_Scenario ... <assertion message>
- Phase 1 test changes after the red commit: none (or: <commit> — <why>)
Resolves <Issue ID>
Linear: https://linear.app/usk6666/issue/<Issue ID>
🤖 Generated with [Claude Code](https://claude.com/claude-code)Notes
- If build or tests fail, fix the issues before re-running
- Determine implementation scope from Issue labels and description
- The design review in Step 4 already serves as the implementation plan for non-trivial Issues — Step 5 just relays it to the user
- Since build/test verification was done in Step 8, do not re-run when creating the PR
- If PR creation fails, guide the user to manually run
/pr - Before completing implementation, verify that the feature is accessible from the config file (no missing config struct, validation, or init function changes)
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.

