carta-cli

Perform deterministic structural edits on .carta workspaces while rewriting docXX.YY references and rebuilding MANIFEST.md.

1|Updated Jan 19, 2026
One-click install
npx skills add https://github.com/saxonthune/carta --skill carta-cli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: carta-cli
Source: https://github.com/saxonthune/carta/tree/main/.claude/skills/carta-cli
Command: npx skills add https://github.com/saxonthune/carta --skill carta-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the pain of reorganizing large, hierarchical documentation sets while keeping numeric references and manifests consistent, so you don’t end up with broken links or stale workspace indexes.

Core Features & Use Cases

  • Deterministic structural operations for .carta workspaces: create, move, delete, punch (file-to-folder), and flatten directory trees while preserving or updating doc references correctly.
  • Automatic ref renumbering and workspace regeneration: rewrites internal docXX.YY refs after renumbering and rebuilds MANIFEST.md so discovery stays accurate.
  • Bulk-safe workflows and repair tools: supports dry runs, deletion output mapping for later rewrites, and a rewrite command to fix stale refs after restores.

Example use case: You inherited a workspace where sections were shuffled and references are now inconsistent; you can restructure using move/delete with gap-closing, then run rewrite based on captured mappings to repair any stale references across the workspace.

Quick Start

Have the agent perform the structural change by running the carta command: move doc04.05 doc04 --order 2 --dry-run.

Frequently Asked Questions about carta-cli

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

FAQPage Schema
How do I reorganize hierarchical documentation without breaking internal references?

Reorganizing hierarchical documentation without breaking internal references requires deterministic structural edits that automatically rewrite docXX.YY refs. This ensures links and workspace indexes remain consistent after moving or deleting files.

How do I renumber documents and regenerate a workspace manifest after restructuring?

To renumber documents and regenerate a workspace manifest after restructuring, apply structural edits that rewrite internal docXX.YY references and automatically rebuild MANIFEST.md to keep workspace discovery accurate.

Can I preview documentation restructuring changes before committing them?

You can preview documentation restructuring changes before committing by running structural operations with a dry-run flag. This simulates moves, deletions, and reference rewrites to reduce the risk of broken links.

What is the best way to close numbering gaps after deleting files from a documentation workspace?

The best way to close numbering gaps after deleting files from a documentation workspace is to use deletion operations with gap-closing logic. This automatically renumbers remaining documents and updates internal references.

How do I fix stale documentation references after restoring files from a backup?

To fix stale documentation references after restoring files from a backup, run a rewrite command using captured deletion output mappings. This repairs inconsistent docXX.YY refs across the entire workspace.

Does restructuring .carta workspaces handle moving attachments alongside their parent documents?

Restructuring .carta workspaces does handle moving attachments alongside parent documents through bundle-aware attachment movement. This ensures associated assets relocate correctly with their directories during structural transformations.