implement-change
Skill1k starsChanged 2 days agoMITView on GitHub
Runs a change of the code from its goal to its review — the main session agrees it with the user and coordinates, a coder subagent implements each task, and other subagents review it before it is shown. Use for every change of the code, the tests or the configs of the repository, whoever asks for it and however small
18 other projects use a version of this.
Trending
More talk lately.about the whole repository
Most recently taken up by
- CsHeng/agent-skillstheir own version, first seen Nov 9, 2026
- Apicurio/apicurio-registrytheir own version, first seen Nov 9, 2026
- 0xdeafcafe/skillstheir own version, first seen Nov 6, 2026
- yaohuangguan/remote-arctheir own version, first seen Nov 1, 2026
- Remote-Arc/remote-arctheir own version, first seen Nov 1, 2026
- Codagent-AI/agent-skillstheir own version, first seen Nov 1, 2026
Who's talking about javierbrea/eslint-plugin-boundaries
- glimpse-hq/Glimpse“Bump the frontend group with 10 updates”GitHub · Nov 9, 2026 · 1 reactions
- JovieInc/Jovie“deps-dev(deps-dev): bump eslint-plugin-boundaries from 6.0.2 to 7.1.0”GitHub · Jul 27, 2026 · 1 reactions
- glimpse-hq/Glimpse“Bump the frontend group across 1 directory with 15 updates”GitHub · Jul 13, 2026 · 1 reactions
- glimpse-hq/Glimpse“Bump the frontend group with 6 updates”GitHub · Jul 6, 2026 · 1 reactions
- @waschlogic.com“Just came across github.com/javierbrea/e... yesterday. I'm sure its overkill for some, but allowing you to …”Bluesky · Apr 4, 2025 · 1 likes
The biggest 5 of 52 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 52
Talked about on GitHub and Bluesky (52 times).
On GitHub · 50
- Nov 9, 2026Bump the frontend group with 10 updates — glimpse-hq/Glimpse1 reaction · 1 comment
- Jul 27, 2026deps-dev(deps-dev): bump eslint-plugin-boundaries from 6.0.2 to 7.1.0 — JovieInc/Jovie1 reaction · 5 comments
- Jul 13, 2026Bump the frontend group across 1 directory with 15 updates — glimpse-hq/Glimpse1 reaction · 2 comments
- Jul 6, 2026Bump the frontend group with 6 updates — glimpse-hq/Glimpse1 reaction · 2 comments
- Nov 10, 2026ci(deps-dev): bump the ci group with 2 updates — rmartz/ai-tools0 reactions
45 more on GitHub
- Nov 10, 2026chore(deps-dev): bump the lint-format group across 1 directory with 2 updates — Krkeek/auto-damm0 reactions
- Nov 9, 2026chore(deps-dev): bump eslint-plugin-boundaries from 7.4.0 to 7.4.2 in the dev-dependencies group — schallym/nestjs-messenger0 reactions · 1 comment
- Nov 9, 2026build(deps-dev): bump the dev-toolchain group across 1 directory with 9 updates — lorem-dev/ailoud0 reactions
- Nov 9, 2026chore(deps-dev): bump the lint group with 2 updates — lance1416/ctws0 reactions
- Nov 9, 2026chore(deps-dev): bump the ci group with 2 updates — rmartz/trip-planner0 reactions
- Nov 9, 2026build(deps-dev): Bump eslint-plugin-boundaries from 7.4.0 to 7.4.1 in the eslint group — withplumix/plumix0 reactions · 1 comment
- Nov 9, 2026chore(deps): Bump the dependencias group with 4 updates — Pavel0990/CERTIC-MAPS-SR0 reactions · 1 comment
- Nov 9, 2026chore(deps-dev): bump the development group with 3 updates — SongNoi/songnoi0 reactions
- Nov 9, 2026chore(deps): bump eslint-plugin-boundaries from 7.4.0 to 7.4.1 in the npm group — jiva-studio/numen0 reactions · 1 comment
- Nov 9, 2026build(deps-dev): bump the development-minor-patch group with 2 updates — VexaMail/vexa-insight0 reactions · 1 comment
- Nov 9, 2026chore(deps-dev)(deps-dev): bump the eslint group across 1 directory with 5 updates — Nks/opentranslate0 reactions · 1 comment
- Nov 9, 2026deps: bump the tooling group across 1 directory with 4 updates — loliman/shortbox-next0 reactions · 1 comment
- Nov 9, 2026chore(deps): bump the minor-and-patch group across 1 directory with 3 updates — minhhuy1201/guild-manager0 reactions · 2 comments
- Nov 8, 2026Bump eslint-plugin-boundaries from 7.4.0 to 7.4.2 — lotfi029/ta3lom_store_web0 reactions
- Nov 8, 2026chore(deps): bump the minor-and-patch group across 1 directory with 10 updates — MaksymovAndrew/portfolio0 reactions
- Nov 8, 2026chore(deps-dev): bump eslint-plugin-boundaries from 7.2.0 to 7.4.1 — gaboluque/blueprint0 reactions
- Nov 7, 2026chore(deps): Bump the dependencies group across 1 directory with 7 updates — stavkamil/blueprint0 reactions
- Nov 7, 2026chore(deps): Bump the minor-patch group with 5 updates — i-sato/ews-ai-agent0 reactions
- Nov 7, 2026chore(deps): bump the minor-and-patch group across 1 directory with 28 updates — Jundev66/CoreBiz0 reactions · 1 comment
- Nov 7, 2026chore(deps-dev): bump eslint-plugin-boundaries from 7.4.0 to 7.4.1 in the ci group — rmartz/pr-shepherd0 reactions
- Nov 7, 2026chore(deps-dev): Bump eslint-plugin-boundaries from 5.4.0 to 7.4.1 — WenYu0306/sage-spatial-agent-guidance-engine0 reactions
- Nov 7, 2026chore(deps-dev): bump eslint-plugin-boundaries from 7.2.1 to 7.4.1 — Keshav-Chaudhary/PlanCraftX0 reactions · 1 comment
- Nov 6, 2026Bump the minor-and-patch group across 3 directories with 13 updates — MaksymovAndrew/cooking-assistant0 reactions
- Nov 6, 2026chore(deps-dev): bump eslint-plugin-boundaries from 5.0.1 to 7.4.1 — dromeas-codereviewbench/retry_final__sentry__dromeas__PR93824__202609040 reactions
- Nov 5, 2026build(deps-dev): bump the development-dependencies group across 1 directory with 10 updates — alexmorris10x/nextjs-saas-boilerplate0 reactions
- Nov 5, 2026Bump the npm group across 1 directory with 25 updates — mykola-blonskyi/spending0 reactions
- Nov 5, 2026chore(deps): Bump the npm-minor-patch group with 6 updates — bhavinvirani/running-coach0 reactions
- Nov 5, 2026chore(deps-dev): bump eslint-plugin-boundaries from 7.2.1 to 7.4.0 — dansilva-98/sistema-adrielli0 reactions
- Nov 5, 2026chore(deps): bump the npm group across 1 directory with 27 updates — Hidoni/lore-world-tracker0 reactions
- Nov 4, 2026chore(deps): bump the web-minor-patch group across 1 directory with 10 updates — GoLe-by-Colding/GoLe0 reactions
- Nov 4, 2026build(deps-dev): bump eslint-plugin-boundaries from 6.0.2 to 7.4.0 — pasaperez/react-frontend-template-ts0 reactions
- Nov 3, 2026Bump eslint-plugin-boundaries from 7.1.0 to 7.4.0 in /web — biloskurskyi/fast_api_posts0 reactions
- Nov 3, 2026chore: bump eslint-plugin-boundaries from 7.2.0 to 7.4.0 — Bori-github/tadaktadak0 reactions
- Nov 2, 2026chore(deps-dev): bump the lint-and-format group across 1 directory with 4 updates — juanpacj-wq/juancespedes.dev0 reactions
- Oct 30, 2026build(deps-dev): bump the lint group across 1 directory with 3 updates — ammarqureshi120/eventmanagement-frontend0 reactions
- Oct 28, 2026chore(deps): bump eslint-plugin-boundaries from 5.4.0 to 7.3.0 — gscalasanz/monorepo0 reactions · 1 comment
- Oct 26, 2026chore(deps-dev): bump eslint-plugin-boundaries from 7.2.0 to 7.2.1 — Revenantal/revenantal-website0 reactions
- Oct 26, 2026chore(deps): bump eslint-plugin-boundaries from 7.2.0 to 7.2.1 — cha2hyun/seed-design-starter0 reactions
- Oct 24, 2026Bump eslint-plugin-boundaries from 6.0.2 to 7.2.0 — adiikj/Argus0 reactions · 1 comment
- Oct 22, 2026chore(deps-dev): bump eslint-plugin-boundaries from 5.0.1 to 7.2.0 — dd-benchmarking/sentry__sentry__deputydev-v2-gpt-5-6__PR95633__202608120 reactions
- Oct 19, 2026Integrate `eslint-plugin-boundaries` — illia-m-b/ticket-guard-action0 reactions
- Oct 12, 2026chore(deps-dev): bump eslint-plugin-boundaries from 5.0.1 to 7.2.0 — Hewline-Ai/sentry__sentry__hew-r2__PR93824__202610120 reactions
- Oct 10, 2026chore(deps-dev): bump eslint-plugin-boundaries from 5.0.1 to 7.2.0 — peer-reviewer-bench/sentry__sentry-greptile__peer-reviewer__PR1__202610100 reactions
- Oct 8, 2026chore(deps-dev): bump eslint-plugin-boundaries from 5.0.1 to 7.2.0 — aether-bench/sentry__sentry__aether-r1__PR95633__202610070 reactions
- Oct 8, 2026chore(deps-dev): Bump eslint-plugin-boundaries from 6.0.2 to 7.3.0 — TheLightbulbCompany/lightbulb0 reactions · 4 comments
On Bluesky · 2
- Apr 4, 2025Just came across github.com/javierbrea/e... yesterday. I'm sure its overkill for some, but allowing you to setup custom rules for what… — @waschlogic.com1 likes and repost
- May 28, 2025With code organization and github.com/javierbrea/e... you can kinda get there. — @waschlogic.com0 likes and reposts · 1 reply
Used with
Projects with it also use audit-test-suite, change-data-safely 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.
yaohuangguanSkillaudit-test-suite
Find where an existing test suite is weak and decide what to test next, ranked by risk. Use this when asked to add missing tests, find gaps, raise coverage, assess test quality or see which areas are thin, even if the request only mentions a coverage percentage.
Also in 3 projects that use this
yaohuangguanSkillchange-data-safely
Change a database schema or stored data without breaking running code or losing data. Use this for any migration, new or changed column, backfill, bulk update, delete, index, or change to a stored format, including in small projects. Data mistakes are often impossible to undo.
Also in 3 projects that use this
BanKnightSkillplan-change
将已完成 spec/design 的 change 拆成可执行 plan 与 tasks。用户要把设计落成执行计划、任务清单或实现步骤时使用。
Also in 6 projects that use this
SauravSrivastavSkilldebug-failure
Diagnose a failing test, command, or runtime behavior using evidence and produce a minimal verified fix.
Also in 3 projects that use this
MicrosoftSkillfix-flaky-test
Reproduces and fixes flaky or quarantined tests. Tries local reproduction first (fast), then falls back to CI reproduce workflow (reproduce-flaky-tests.yml). Use this when asked to investigate, reproduce, debug, or fix a flaky test, a quarantined test, or an intermittently failing test.
Also in 3 projects that use this
srclightSkillrefactor-safely
This skill should be used when the user asks to "refactor", "rename", "move", "change a function signature", "extract a method", "delete unused code", "clean up", or any modification that could break callers or dependents. Provides a pre-change safety checklist using srclight's graph tools to assess blast radius before touching code.
Also in 5 projects that use this
- +6 more from yaohuangguan
Other versions18 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 18
- pnpm/pnpm★ 37ksame name
- verdaccio/verdaccio★ 18ksame name
- Apicurio/apicurio-registry★ 958same name
- Codagent-AI/agent-skills★ 31same name
- manhds82/claude-code-anyllm★ 16same name
- taljeon/plzdo★ 9same name
- yaohuangguan/remote-arc★ 5same name
- CsHeng/agent-skills★ 3same name
- otaviobarros/agent-engineering★ 3same name
- EJRyan89/coding-agent-skills★ 2same name
8 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.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- address-review-commentsSkill
- boundaries-architectSkill
- create-architectural-decision-recordSkill
- create-issueSkill
- create-prSkill
- documentation-writerSkill
- releaseSkill
- repo-architectureSkill
- review-prSkill
- unit-testingSkill
- write-planSkill
- writing-styleSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 17 edited versions we read keep these.
1
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 32
Understand the change: Read the request, the phase of the plan when the session belongs to one, and the AGENTS.md of each project the …
- Very specific: line 45
Stop after the third round that still leaves a blocking finding, and tell the user what is left and why it does not converge.
“Common” is measured: kept by at least 6 in 10 of the 17 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 a change
When to use
For every change of a file under packages/, examples/, support/, test/, scripts/, .github/workflows/ or .husky/, or of a config at the root. A release is run by the release skill instead.
Sizing the change
| The change | Size | Designed by | Agreed with the user | Reviewed by |
| Stays inside one element of one project, after a pattern the project already has | Contained | The main session | Only what the request leaves open | reviewer |
| Crosses a boundary between projects or between the elements of one, after an existing pattern | Architectural | architect | Always, as references/agreeing-the-change.md says | reviewer and architecture-reviewer |
| Adds a package, an element type, a public export, an entry point, a dependency between packages or a pattern, or changes an invariant or a decision of the plan | Architectural and new | architect, then skeptic | Always, the same way | reviewer and architecture-reviewer |
- When in doubt, the change is of the larger size.
- A contained change that turns out to cross a boundary stops, and starts again as architectural.
Who does what
- The main session coordinates the whole change and keeps its context, which no subagent sees. It delegates the code, never the judgment of the design, and does not write the code itself.
- A subagent sees only its brief. Whatever it needs from the conversation goes in it.
- A
codernever commits and never decides a placement. The other subagents edit nothing. - Only the main session commits, what passed its review, and only when the user or the plan asks for it. Before each commit,
git diff --cached --name-onlylists only the files intended.
Procedure
- Understand the change. Read the request, the phase of the plan when the session belongs to one, and the
AGENTS.mdof each project the change touches. Size it. - Agree it. An architectural change follows
references/agreeing-the-change.md: no code is written before the user approves its goal, its design and how it is accepted. A contained one is placed by the session after theAGENTS.mdof its project, and the user is asked only what the request leaves open.- Either way, this step ends with the goal, how the change is accepted, and a list of tasks, each with its files, the interfaces it crosses and its tests. The
CHANGELOG.mdentries that.agents/rules/changelog-and-versioning.mdrequires belong to the tasks.
- Either way, this step ends with the goal, how the change is accepted, and a list of tasks, each with its files, the interfaces it crosses and its tests. The
- Implement it. Delegate each task to a
coder, with the brief below. Two tasks run at once only when they share no file and neither of their projects depends on the other; the others run in the order of the design. - Read what each coder returns. A deviation from the brief is accepted with its reason or sent back. A question is answered from the docs or taken to the user, never guessed.
- Run the checks:
pnpm nx affected -t check:all --base=<the branch the change started from>;pnpm lintandpnpm check:spellat the root, which no Nx target runs; and, for each changed source file of a package withtest:mutation, specs excluded, the run scoped to it that.agents/rules/mutation-testing.mdgives. A failing check goes back to acoder, and so does each surviving mutant, until it is killed or commented as that rule says. - Review the whole change yourself, reading its full diff against the design:
- Each file is where the design placed it, and the change crosses only the interfaces of the design.
- Nothing changed outside the tasks, such as a script or a broken behavior left behind by a coder.
- The agent docs and the
README.mdof each project touched are still true, or are updated now.
- Have it reviewed by the subagents its size asks for, at once, each with what the change is for, how it is accepted, its design and the range of the diff. Never give them what the coder concluded or what you expect them to find.
- Check each finding before acting on it, yours included, as "Checking a finding" says.
- Fix what is true. Send the true findings to a
coder, each with its evidence, run the checks of step 5 again, and have the reviewer that raised each one review only what the fix changed.- Stop after the third round that still leaves a
blockingfinding, and tell the user what is left and why it does not converge.
- Stop after the third round that still leaves a
- Check each item of how it is accepted.
- Report what "The report" lists.
The brief of a coder
- The goal, and what it is for, in two sentences.
- The files to create or edit, each with its project and its element, and the example to copy as a path.
- The interfaces the task crosses, with their exact shape.
- What it must not touch, such as the files of a task that runs at once.
- The tests: each behavior to cover, and each existing test to rewrite or move.
- A folder of its own for scripts and temporary files, outside the repository, so that coders running at once never share one.
- How it is accepted: the commands that must pass.
- In a round of fixes: each finding with its
file:lineand its evidence.
Checking a finding
A finding is a claim about the code, and whoever raises it can be wrong. Check it by the cheapest way that can show it false:
| The finding says | Check it by |
| The code does something wrong | A test or a command that shows the wrong result |
| A rule or an invariant is broken | Reading the rule, and the line that breaks it |
| A boundary is crossed | The lint of the project, or its eslint.config.* when the lint cannot see it |
| A test proves nothing | Breaking the behavior and running the test |
| A case is not handled | Running that case |
| A library or a tool behaves in some way | Its source, its types or a run of it, never what it is known for |
Each finding ends as one of three:
- True: it goes to the round of fixes, or changes the design.
- False: it is dropped, and kept with its evidence for the report.
- A matter of taste, or a change of what was agreed: decided from the docs when they settle it, and asked to the user when they do not.
- A check that changes a file is undone, such as a behavior broken to try a test.
- Never drop a finding because fixing it is expensive, and never fix one that was not checked.
The report
- What changed, by project, and the design decisions behind it.
- Each item of how it is accepted, with its result.
- The findings fixed, and those dropped, each with its evidence.
- The checks run, with their real result.
- What is left: what could not be checked, what was found outside the change, and what waits for the user.
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.

