archlang-edit-plan
Use when the user wants to change an existing ArchLang .arch floor plan, e.g. "make the bedroom 1 m wider", "add a bathroom next to the hall", "move the front door to the south wall", "merge the kitchen into the living room". Reads the plan's facts with the archlang CLI, makes the smallest edit that does the job, and re-verifies. Not for writing a plan from a brief (archlang-brief-to-plan).
How do I install this agent skill?
npx skills add https://github.com/chanmeng666/archlang --skill archlang-edit-planIs this agent skill safe to install?
- Gen Agent Trust Hubpass
This skill facilitates editing .arch architectural floor plans using the archlang CLI tool. It involves downloading an external package and processing external data files, which introduces a standard indirect prompt injection surface.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
What does this agent skill do?
Edit an existing plan
Change a .arch file without breaking what already works.
If archlang is not on the path, write npx -y @chanmeng666/archlang in its place.
Never run a bare arch: on Linux, macOS and Git Bash that name is the coreutils command.
This skill is a workflow, not a language reference. Run archlang spec for the language and
archlang <cmd> --help for a command's flags.
Scope
- Run the
archlangCLI commands below and no other program. - Change the one
.archfile the user asked you to edit (plan.archbelow). If the user has not named it, ask. Besides it, write only the drawing the CLI renders and the.bakcopy that--backupkeeps. - The user's explicit instructions take priority over these steps.
Steps
- Record the starting state. Run
archlang validate plan.arch --jsonandarchlang describe plan.arch --select rooms,totals --json. Keep both results: they are what you compare against at the end. If the plan already has errors, tell the user before you edit. - Choose the locks, then check the edit. Before you edit, list the ids the request does not
name: those are the locks. For a change to one top-level
let, ask first, with nothing written:archlang impact plan.arch --set NAME=value --lock <ids> --json. For any other edit, make it in a copynew.archand check it after:archlang impact new.arch --against plan.arch --lock <ids> --json. Exit2withE_LOCKED_ELEMENT_CHANGEDnames a locked element the edit moves: change the edit, not the lock. A lock names elements by theid=written in the source (an unnamed one is refused withE_LOCK_UNNAMED). - Read only what the change touches.
archlang describe plan.arch --room <ids> --jsonreturns those rooms with the doors, windows and furniture that touch them.archlang describe plan.arch --select freedom --jsonsays which positions the author typed (absolute) and which the compiler derives. Change a typed number; a derived one moves by itself when the thing it depends on moves. - Read the language for the forms you will write.
archlang spec. - Make the smallest edit. Change the statements the request names and leave the rest as they are: same ids, same order, same comments. Do not reformat the file and do not rewrite statements you were not asked to change. When a room changes size, check the walls, doors, windows and neighbouring rooms that share its edges.
- Compile.
archlang compile plan.arch -o plan.svg --json. Ifokis false, preview the mechanical fixes witharchlang fix plan.arch --dry-run --jsonand read the diff before you apply them witharchlang fix plan.arch --backup. - Move furniture out of the way if needed. If the edit pushed a piece into a wall, a doorway
or a door swing,
archlang repair plan.arch -o plan.archmoves it. Readunresolvedfor the pieces it could not move. - Verify the change and nothing else. Run the two commands from step 1 again, and
the
impactcheck from step 2 on the edited file. The rooms you meant to change differ as intended. Every other room has the same area and the same connections. No diagnostic is new unless the request causes it; if one is, tell the user. - Refresh the sheet if the drawing grew.
archlang finish plan.arch --dry-run --jsonshows what is missing. If it reports that the drawing no longer fits the authoredpaperorscale,archlang finish plan.arch --reissuemay replace those two statements and nothing else.
When another agent may edit the same file
Pass the file's current revision as --expected-hash <hash>, as in
archlang fix plan.arch --expected-hash <hash> --json. The --json result of each command that
rewrites the file (fix, finish, repair -o plan.arch, fmt --write) says which hash that is:
source_hash is the file as the command read it, and written_hash the file once the command has
written it. A result that hands you rewritten text instead (repair --json, a --dry-run, or the
MCP repair, fix and finish tools) gives output_hash, the file's revision once you write that
text to it unchanged. archlang fmt plan.arch --json reports source_hash without writing, even
when it refuses a plan that does not parse (exit 2, ok: false, parsed: false). If the
file changed since, the command writes nothing and exits 4 with E_STALE_SOURCE: read the file
again, redo your edit on what is there now, and use the new hash. This narrows the window for a
clash; it is not a lock.
Report to the user
- The statements you changed, as a short diff.
- Before and after for the facts the request is about (for example the room's area).
- Any new warning, and whether the request causes it.
When something goes wrong
- Exit code
2is a fault in the source: read the diagnostic, do not retry unchanged.3is a wrong flag: runarchlang <cmd> --help. archlang explain <CODE> --jsonexplains a diagnostic code.- If the request needs a new door or window and you are unsure where it can go,
archlang suggest plan.arch --jsonreturns candidates with the reason for each.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/chanmeng666/archlang/archlang-edit-plan">View archlang-edit-plan on skillZs</a>