update-arch

Refreshes changed sections of prose architecture documentation without a full codebase re-scan.

1|Updated Jun 27, 2026
One-click install
npx skills add https://github.com/vickysrawat/AI-Assisted-development --skill update-arch-vickysrawat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-arch
Source: https://github.com/vickysrawat/AI-Assisted-development/tree/main/skills/update-arch
Command: npx skills add https://github.com/vickysrawat/AI-Assisted-development --skill update-arch-vickysrawat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping architecture documentation accurate after code changes normally requires an expensive full re-scan of the codebase, so docs drift out of date. This Skill re-reads only the changed parts of the codebase and updates just the affected sections of the prose architecture docs, at roughly 5-10% of the cost of a full architect run. ## Core Features & Use Cases - Targeted refresh: Auto-detects changed source areas via git history (or accepts a subtree path) and updates only the corresponding sections of architecture.md, leaving everything else verbatim. - Mode flags: --deployment re-runs the deployment questionnaire, --data / --integrations / --security regenerate individual architecture doc files, and --decisions appends a new AD-NNN entry to the decisions log without touching existing entries. - Consent-gated reads: Applies a Category B source-file consent gate before reading changed entry-point files, and never touches the knowledge graph (that is /graph-sync's job). - Use Case: After refactoring the matters service, run /update-arch src/services/matters/ to refresh only that section of the architecture docs, then run /graph-sync separately if module structure changed. ## Quick Start Ask the AI to run /update-arch with no arguments to auto-detect changed areas and refresh the affected sections of the architecture documentation.

Frequently Asked Questions about update-arch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update architecture documentation after code changes?

Run /update-arch with no arguments to auto-detect changed source areas from recent git commits, or pass a subtree path like src/services/matters/ to scope the refresh. Only the affected sections of architecture.md are rewritten; everything else stays verbatim.

What is the difference between /update-arch and /setup-init?

/update-arch performs a targeted refresh of changed sections at roughly 5-10% of the cost of a full run, while /setup-init regenerates all architecture docs from scratch. Use /setup-init when no architecture.md exists yet or for a complete re-scan.

Does /update-arch update the codebase knowledge graph?

No. The module orientation graph under .claude/graph/ is refreshed separately by /graph-sync, which is fingerprint-based and incremental. /update-arch only touches the prose architecture.md and related doc files.

How do I re-run the deployment questionnaire without a full architecture scan?

Run /update-arch --deployment. It forces the architect deployment questionnaire to re-run even if architecture-deployment.md is already complete, pre-filling existing answers as defaults, then writes and verifies the updated file.

Can /update-arch add a new architecture decision record?

Yes. Run /update-arch --decisions to append a new AD-NNN entry to architecture-decisions.md with decision, rationale, alternatives rejected, date, and status. Existing entries are never modified or removed.

Why does /update-arch ask for consent before reading source files?

It applies a Category B source-file consent gate before reading changed entry-point files, presenting one consolidated request listing files, purpose, and token cost. Declining leaves the affected architecture.md sections unchanged and notes that they were not refreshed.