Archrip update
Update or refine the architecture diagramFrom its SKILL.md
npx -y skills add yida29/archrip --skill archrip-updateAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.3 KB, as published. Nobody here has run it
archrip update — Update architecture diagram
Read .archrip/architecture.json and update it.
Mode 1: Auto-detect from git diff (no arguments)
If $ARGUMENTS is empty:
- Run
git diff --name-only HEAD~10to find changed files - Read the current
.archrip/architecture.json - For each changed file:
- New component? → Add node + edges
- Removed component? → Remove node + edges + use case references
- Changed dependencies? → Update edges
- Preserve existing node IDs for unchanged components
- Write updated
.archrip/architecture.json
Mode 2: Apply requested changes (with arguments)
If $ARGUMENTS is provided, apply the user's requested changes:
- Add/remove/modify nodes
- Fix relationships
- Add/modify use cases
- Adjust layer assignments
- Add database schemas
- Add/modify metadata entries
- Improve descriptions
Write the updated .archrip/architecture.json.
Schema constraints (apply on every write)
When adding or splitting nodes, follow the same rules as the scan skill:
- One node per real component. Avoid umbrella nodes that bundle siblings — each Controller, UseCase, abstract Repository, Repository implementation, and Domain Entity is normally its own node. See archrip-scan/schema-reference.md → Node Granularity.
- Repository → Port pattern (DDD/Hex). Every abstract Repository becomes a
portnode in the application core; every implementation becomes anadapternode thatimplementsthe port. Use cases depend on the port, not the adapter. See archrip-scan/schema-reference.md → Repository → Port pattern. implementsedges flowadapter → port. Never point them at entities, adapters, or databases — that signals a missing port abstraction. See archrip-scan/schema-reference.md → Edge type semantics.
After Update
After writing the file, run npx archrip serve in the terminal to rebuild and preview the updated diagram.
$ARGUMENTS