coordinate-edit

Check Kuro cycle status and validate git branch before editing src/ or memory/.

3|1|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/miles990/mini-agent --skill coordinate-edit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coordinate-edit
Source: https://github.com/miles990/mini-agent/tree/main/.claude/skills/coordinate-edit
Command: npx skills add https://github.com/miles990/mini-agent --skill coordinate-edit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill prevents conflicting edits to the mini-agent repo by coordinating with Kuro’s active perception cycle and enforcing safe branching/worktree rules before you touch src/ or memory/.

Core Features & Use Cases

  • Checks whether Kuro is busy: Queries the local status endpoint and warns when an active cycle could react to file changes.
  • Validates the current branch: Detects the runtime/main branch and warns that tracked changes there may be autocorrected away.
  • Optionally announces intent: Posts an occupancy claim to the chat-room using an API key, helping resolve edit conflicts.
  • Provides a pre-action checklist: Summarizes the coordination steps to follow before making larger modifications.

Quick Start

Run the coordinate-edit script once before editing src/ or memory/ to get a read-only coordination report, and add an announcement message if you need to claim ownership of the change.

Frequently Asked Questions about coordinate-edit

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

FAQPage Schema
How do I prevent conflicting git branch edits in an active agent workspace?

To prevent conflicting git branch edits, you must validate the current branch and check if an active perception cycle is running before modifying files. This involves querying a local status endpoint and optionally announcing edit intent to claim workspace ownership.

Why does my file change get autocorrected away on the runtime/main branch?

File changes on the runtime/main branch get autocorrected away because an active perception loop reacts to and reverts modifications. Validating the current git branch before editing ensures you avoid branches subject to automatic corrections.

What is the best way to coordinate repo edits with a local perception loop?

The best way to coordinate repo edits with a local perception loop is to query the local API status endpoint before making changes. This checks if the cycle is busy and allows you to post an occupancy claim to the chat-room to announce edit intent.

Do I need a local API connection to announce edit intent in the chat-room?

Yes, you need a reachable local API at http://127.0.0.1:3001 to announce edit intent. The coordination script uses curl to query the status endpoint and posts an occupancy claim to the chat-room using an API key to help resolve edit conflicts.

When should I run a pre-action coordination check before modifying src/ or memory/ directories?

You should run a pre-action coordination check before making larger modifications to src/ or memory/ directories. This is especially important when changes risk interfering with an active perception loop or when operating on tracked branches like runtime/main.