update-workspace-map

Regenerate the workspace map after file changes or commits.

3|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/adihebbalae/Attacca --skill update-workspace-map-adihebbalae
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-workspace-map
Source: https://github.com/adihebbalae/Attacca/tree/main/addons/kiro/.kiro/skills/update-workspace-map
Command: npx skills add https://github.com/adihebbalae/Attacca --skill update-workspace-map-adihebbalae

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Manages and updates the .agents/workspace-map.md to reflect changes in your codebase, ensuring multi-agent codebases stay current and prevent outdated mappings.

Core Features & Use Cases

  • Automated Map Regeneration: Updates the workspace map automatically after file changes or post-commit operations.
  • Scalability: Handles new files, deleted files, moved files, and new directories to maintain accuracy.
  • Preventive Measure: Mitigates the risk of agents working with outdated or incorrect workspace mappings.
  • Use Case: Ensures that during development, all agents are correctly pointed to the correct files in the codebase, reducing the risk of errors.

Quick Start

Run the 'update-workspace-map' skill after making changes to your workspace or after a commit to update the workspace map.

Frequently Asked Questions about update-workspace-map

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

FAQPage Schema
How do I keep a workspace map updated for multi-agent systems?

To keep a workspace map updated for multi-agent systems, you need an automated process that regenerates the mapping post-commit. This ensures all agents operate with the latest codebase state and prevents outdated file references.

What is a post-commit workspace map regeneration?

Post-commit workspace map regeneration is the automated process of updating codebase mappings after file changes are committed. It handles new, deleted, and moved files to maintain mapping accuracy for multi-agent environments.

Why do multi-agent systems work with outdated codebase mappings?

Multi-agent systems work with outdated codebase mappings when file changes are not synchronized across the environment. Running an automated map update post-commit mitigates this risk by reflecting the latest directory and file states.

How do I update workspace maps after moving or deleting files?

To update workspace maps after moving or deleting files, run an automated regeneration script post-commit. This scales to handle new directories and deleted files, keeping the codebase mapping accurate for all agents.

What is the best way to prevent agents from referencing incorrect files?

The best way to prevent agents from referencing incorrect files is to automate workspace map regeneration after codebase changes. This ensures agents are correctly pointed to current files, reducing development errors.