build-feature
Skill2 starsChanged 5 months agoMITView on GitHub
Walk the feature-build protocol when adding/creating/building/implementing a new feature — classify type, run near-match scan, FCPSS, tier-correct review.
14 other projects use a version of this.
Adopted by
Most recently taken up by
- Doist/todoist-aitheir own version, first seen Nov 9, 2026
- Doist/todoist-clitheir own version, first seen Nov 8, 2026
- sbradl/claude-skillstheir own version, first seen Oct 15, 2026
- koruworks/skillstheir own version, first seen Oct 15, 2026
- zyggy-org/zyggytheir own version, first seen Oct 13, 2026
- sirakinb/claude-code-skillstheir own version, first seen Oct 11, 2026
Used with
Projects with it also use fix-bug, write-tests and 1 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.
JetBrainsSkillfix-bug
End-to-end bug fix workflow for the Exposed project. Accepts a GitHub issue (#NUMBER), YouTrack issue (EXPOSED-NUMBER), or YouTrack URL (https://youtrack.jetbrains.com/issue/EXPOSED-NUMBER). Fetches the issue, creates a failing reproducer test, commits on a new branch, implements the fix, validates, and opens a PR. Use this skill whenever the user wants to fix a bug from an issue tracker, mentions a EXPOSED issue number, or references a GitHub issue to fix.
Also in 5 projects that use this
SentrySkillwrite-tests
Write tests following project conventions. Use when adding new tests or modifying existing ones.
Also in 3 projects that use this
GitHubSkillrefactor
Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.
Also in 3 projects that use this
Other versions14 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 14
- signerlabs/ShipSwift★ 3.3ksame name
- Doist/todoist-ai★ 563same name
- Doist/todoist-cli★ 331same name
- AlemTuzlak/skills★ 45same name
- Guild-Agents/guild★ 4same name
- garthcodes/claude-skills★ 2same name
- zyggy-org/zyggy★ 2same name
- evgenii-studitskikh/Claude-Code-SaaS-Studio★ 1same name
- sirakinb/claude-code-skills★ 1same name
- koruworks/skills★ 0same name
4 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 repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- doc-consistencySkill
- refactor-extractSkill
- refresh-vendorSkill
- build-featureSkill
- doc-consistencySkill
- refactor-extractSkill
- refresh-vendorSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 13 edited versions we read keep these.
0
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
- Very specific: line 20
If the scan in step 3 surfaces a candidate where extension wins, enter refactor-extraction.md at the Execute phase directly (authoring-time …
“Common” is measured: kept by at least 6 in 10 of the 13 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
/build-feature
Substance lives in markdowns/protocols/build-feature.md.
Steps:
- Discriminate kickoff vs iteration per
auto-trigger-discriminator.md. If iteration / polish / investigation, exit silently. Explicit/build-featureinvocation bypasses and walks the full protocol. - Classify the feature. Note the stake tier from
stake-matrix.md. - Run the near-match scan. Up to 5 nearest existing helpers by file proximity + name-token overlap + signature shape. For each candidate, answer: would extension be ≥70% applicable? Extension wins by default; if rejecting extension, document the reason.
- Draft FCPSS coverage per
fcpss-gate.md. - Implement. Pre-commit hooks are the syntactic gate; FCPSS + tests are the semantic gate.
- Review per tier per
stake-matrix.mdandsupervision.md: Tier 1/2 = cross-vendor mandatory + chat-checkpoint + wait for "ship it"; Tier 3 = same-vendor self-review; Tier 4 = pre-commit only. - Ship gate. FCPSS clean, tests pass, pre-commit clean, tier-correct review done.
If the scan in step 3 surfaces a candidate where extension wins, enter refactor-extraction.md at the Execute phase directly (authoring-time near-match bypasses the mechanical-signal gate).
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.