code-atlas:update

Incrementally update Code Atlas architecture index entries using file-hash diffing.

Updated Jul 1, 2026
One-click install
npx skills add https://github.com/MisterVitoPro/qa-swarm --skill code-atlas-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-atlas:update
Source: https://github.com/MisterVitoPro/qa-swarm/tree/main/plugins/code-atlas/skills/update
Command: npx skills add https://github.com/MisterVitoPro/qa-swarm --skill code-atlas-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Incrementally updates the Code Atlas architecture index as the codebase evolves, re-indexing only changed areas to minimize work and downtime.

Core Features & Use Cases

  • Incremental diffing between the current and baseline state to update atlas indices without a full rescan.
  • Supports micro-update, targeted update, and full re-scan via a 'full' argument.
  • Use case: when you modify a subset of files, the tool updates only affected atlas entries and preserves overall index integrity.

Quick Start

Invoke the code-atlas:update skill with an optional full argument to perform a full re-scan when needed.

Frequently Asked Questions about code-atlas:update

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

FAQPage Schema
How do I incrementally update an architecture index without rescanning the entire codebase?

To incrementally update an architecture index, the Code Atlas uses file-hash diffing against state.json to identify changed files, updating only affected entries rather than performing a full rescan.

What is the best way to trigger a full re-scan of a code architecture index?

You can trigger a full re-scan of the architecture index by invoking the update skill with a 'full' argument, which forces the complete map pipeline to rebuild all entries from scratch.

How does file-hash diffing work for state management in codebase indexing?

File-hash diffing works for state management by comparing current repository files against a baseline state.json, allowing the index to process only modified areas and preserve overall index integrity.

Can I perform targeted updates to specific architecture index entries?

Yes, you can perform targeted updates to the architecture index. The skill supports micro-updates and targeted updates to modify specific entries when only a subset of files changes.

Where does the architecture indexing tool store its state and index data?

The architecture indexing tool reads and writes its state and index data exclusively within the `.code-atlas/` directory to maintain baseline state and manage incremental updates.

When should I avoid incremental indexing and rebuild the architecture map completely?

You should avoid incremental indexing and rebuild completely when overall index integrity is compromised, or when major structural changes occur, by using the 'full' argument to trigger a complete re-scan.