agentleFS
Sign inStart free
zoranmarticzoranmartic/coord-wright/skills/coord-promote/SKILL.md

coord-promote

Skill0 starsChanged 47 days agoApache-2.0View on GitHub

Promote one or more shaped coord tasks to pending, then commit and push. Zero args promotes every task in status:shaping. Use when the user says "/coord-promote", "promote <id>", or "promote all shaping tasks".

  • Commits and pushes

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 3 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If $ARGUMENTS is non-empty: split on whitespace/commas to get the id list.

    line 17
  2. Very specific:

    If $ARGUMENTS is empty: run python3 "${COORD_TOOLS:-$HOME/Projects/coord-wright}/bin/coord" list --status=shaping --format=ids and use the …

    line 18
  3. Very specific:

    Run python3 "${COORD_TOOLS:-$HOME/Projects/coord-wright}/bin/coord" paths --json to get tasks_dir, then git status --porcelain "$tasks_dir" …

    line 21
  4. Distinctive:

    If any exist, print a warning listing each filename, then continue — do not abort.

    line 22
  5. Distinctive:

    If any invocation exits non-zero: print the failing id and its stderr, then stop immediately.

    line 28
  6. Very specific:

    Never use --no-verify or --force.

    line 36
  7. Very specific:

    If coord promote rejects an id (shaping warning, missing plan, etc.), surface the error as-is — the task is not ready.

    line 37
  8. Distinctive:

    Keep output terse; no extra commentary beyond the per-id lines and the commit/push result.

    line 38

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Flip shaped tasks to pending and publish atomically. The launchd coord loop reads local files, so promote → commit → push must run as a tight sequence with no pauses.

Project-root preflight:

  • Resolve the canonical project checkout before listing tasks, promoting, staging, committing, or pushing: COORD_MAIN=$("${COORD_TOOLS:-$HOME/Projects/coord-wright}/bin/coord-project-root") && cd "$COORD_MAIN"
  • This is required when the skill is invoked from a sibling task worktree; promotion must update the main queue that the launchd worker reads.

Workflow

  1. Resolve target ids.
    • If $ARGUMENTS is non-empty: split on whitespace/commas to get the id list.
    • If $ARGUMENTS is empty: run python3 "${COORD_TOOLS:-$HOME/Projects/coord-wright}/bin/coord" list --status=shaping --format=ids and use the output as the list. If output is empty, report "no shaping tasks found" and stop — do not commit.
  2. Pre-check for unrelated dirty coord files.
    • Run python3 "${COORD_TOOLS:-$HOME/Projects/coord-wright}/bin/coord" paths --json to get tasks_dir, then git status --porcelain "$tasks_dir" and collect any modified coord task files whose base name (without .md) is NOT in the promote set.
    • If any exist, print a warning listing each filename, then continue — do not abort.
  3. Promote each id.
    • For each id in the list, run: python3 "${COORD_TOOLS:-$HOME/Projects/coord-wright}/bin/coord" promote <id>
    • coord promote auto-commits-and-pushes each task individually. Do not run manual git add, git commit, or git push.
    • If any invocation exits non-zero: print the failing id and its stderr, then stop immediately. Do not retry or look for a bypass.
  4. Report.
    • One line per promoted id: promoted: <id>.
    • Note: each promotion is its own commit; multi-id batching into a single commit requires a CLI-level change that does not yet exist.

Rules

  • Never use --no-verify or --force.
  • If coord promote rejects an id (shaping warning, missing plan, etc.), surface the error as-is — the task is not ready.
  • Keep output terse; no extra commentary beyond the per-id lines and the commit/push result.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free