Install Claude Code Bundles Without Breaking Your Own Files
Copying Claude Code bundles by hand misplaces files and hides stale versions. npx agentic-fx@latest install records every file it writes in .claude/.agentic-fx.json, and update and uninstall touch only files on that list.
Key takeaways
- Copying Claude Code bundles by hand puts files in the wrong place, can leave a second bundle without its hooks, and gives no sign that a copy is stale.
- npx agentic-fx@latest install copies a bundle's agents, commands and skills into .claude/, its workspace into .sdlc/, .stlc/ or .evals/, and merges its settings.json rules and hooks.
- Every file the installer owns is recorded in .claude/.agentic-fx.json, and update and uninstall act only on files on that list.
- Your profile and your own settings.json rules survive an update; a file a new version no longer ships is deleted only after you confirm.
- doctor reports a missing .claude folder, and outdated shows installed against published versions for each bundle.
Contents
FAQ
Which bundles does npx agentic-fx@latest install?
It installs dev (software delivery), qa (testing) and eval (LLM and agent evaluation) with `--bundle dev,qa,eval` or `--bundle all`. With no flag it asks, and with `--yes` and no flag it installs all three.
Does an update overwrite my profile or settings?
No. The profile (`DEV-PROFILE.md`, `PROJECT-PROFILE.md` or `EVAL-PROFILE.md`) is kept, and settings.json only gains rules and hooks it lacks. Files the bundle owns are replaced, so edit the profile, not the bundle files.
How do I skip the VS Code board?
Pass `--no-addons`. Without it, the board is installed into VS Code, Cursor or Windsurf, whichever command is found on the machine.
Sources
Only you and the owner see your answer and rating. Send private feedback
Enjoyed it? Support fx-blog with a coffee.
Related posts
The QA Board and the Release Gate
"May it ship?" should not be answered in a chat. The stlc board on orders checkout, and a QA release gate: a report verdict derived from its gate rows, rejected by lint if it disagrees, which the dev deploy step reads before checkout ships.
When a Test Goes Red: Triage, the Heal Guard and Quarantine
The cheapest fix for a red AI test is to hide it. On checkout a red test is labelled, not fixed: four triage labels, a heal guard that diffs every fix, quarantine that expires in 30 days, and a defect that closes only on a newer passing run.
Your First stlc Run: Checkout From Docs to Scripts
You cannot tell whether AI-written tests cover the spec. The first stlc run on orders checkout: requirement ids, a traceability table created with zero rows where each column has one writing step, a case review, and ten scripts.
Comments
Oldest firstNo comments yet. Start the conversation.
You copy a bundle's agents, commands and skills into
.claude/on Monday. The bundles here aredev(software delivery),qa(testing) andeval(LLM evaluation).A month later a fix ships. You copy again, over the file you tweaked. Or you don't. Nothing tells you which.
What goes wrong when you copy by hand
None of it throws an error. A file in the wrong folder just sits there. Two bundles each ship a
settings.json; copy the second over the first and one bundle runs without its hooks. And a copied folder has no version, so you can't tell it is stale.Five questions to ask of any installer
.claude/.agentic-fx.jsonuninstalldeletes listed files onlyHow the installer works, step by step
--bundle dev,qa,evalorall; with no flag it asks. It checks Node 20+, Claude Code, Git Bash on Windows and Python foreval, and blocks on none..claude/, the workspace to.sdlc/,.stlc/or.evals/. A profile is copied only if you have none.settings.json.--no-addons.Step 3 is where this differs from the installer I use in-house. That one leaves a second settings file for you to merge by hand. Fine for me. Someone installing two bundles from npm would run the second with its hooks silently off, so this one merges, and only ever adds.
One real run: a deleted folder and an old version
An empty git repo called
my-project, thennpx agentic-fx@latest install --bundle dev,qa --no-addons --yes:ls -AF -C -T 0 -w 76 .claude .sdlc .stlcshows where it went. The manifest lists 507 files.Then I broke it. A line in
DEV-PROFILE.md, a permission rule of my own insettings.json,rm -rf .claude/skills, andnpx agentic-fx@latest doctor:npx agentic-fx@latest update --no-addonsput the skills back.tail -n 1 .claude/DEV-PROFILE.mdstill printed my line, my rule was still there, anddoctorwent green.Last, I set
devto 1.8.0 in the manifest, standing in for an older install, and rannpx agentic-fx@latest outdated:npx agentic-fx@latest update --bundle dev --no-addonsmoved it to 1.10.0. A MAJOR release would ask first.Get it
Fill the profile, then run
/sdlc-intake <slug>,/qa-analyze <slug> <docs…>or/eval-scope. You need Node 20+ and Claude Code.What does a gate in
devactually check? Read Your AI Coding Agent Grades Its Own Homework. Add Gates. Testing starts with A QA Pipeline Your AI Agent Can't Fake.Read this with your AI