pnyx-arrange-columns
Skill4 starsChanged 2 days agoApache-2.0View on GitHub
Use when you are Hydra and are about to move or reorder a card, or create, rename, describe, rule, reorder, delete or resize a Hydra column.
In this repository17 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- audit-testsSkill
- deslopSkill
- follow-conventionsSkill
- review-codeSkill
- write-ci-workflowSkill
- write-front-endSkill
- write-pull-requestSkill
- write-skillSkill
- inscribeSkill
- pnyx-cliSkill
- pnyx-firstmate-as-hydraSkill
- pnyx-manage-workersSkill
- pnyx-orchestrateSkill
- pnyx-report-progressSkill
- pnyx-set-upSkill
The file
Files
Hydra columns
Each column has a rule that code applies without a model. The digest lists column names, task counts and descriptions. Read pnyx-axi column list --hydra <hydra> for placement rules before changing columns. When the owner asks for a column change, write or update its rule so future events and commands place cards there automatically.
Move a card
Pnyx computes facts from the recorded worker state, owner questions, discussion hold, pull requests, task kind, completion, reminders and queue. The first column in display order with a matching rule wins. Successful starts and queue handoffs record working; owner questions, permissions, merge and go questions, or due reminders go to Needs you. Worker needs_you and blocked notes stay In progress for Hydra to resolve. A worker paused for checks stays In progress; an owner pause or an ended worker with unfinished work goes to Parked. Held unfinished work stays in Backlog (the Queued role), marked Talking, until a real go question puts it in Needs you. Checked done declarations and all non-abandoned linked pull requests merging place completed work in Done, even with a discussion hold. The hold remains and applies again if the task reopens. A finished turn or successful session never declares completion. On Firstmate-linked Hydras, Firstmate's records own placement.
Use move for an owner request or an exceptional correction with a reason. A manual placement, including one in a custom column, holds until the next change in the matching rule's destination. Ordinary activity, repeated status notes and edits that match the same destination leave it alone.
pnyx-axi move <task> <column> --reason "<why>" --hydra <hydra>Inspect the proposed action, then repeat the command with --confirm <token>.
Rely on the worker's checked done declaration or Pnyx's merge transition. If completion evidence is missing, ask the worker to record it and declare the result. Do not repeat its status or move the card to Done yourself. Passing local checks alone is not completion.
Change columns
Use column rule <id> --when "<fact>[,<fact>]" --reason "<why>" to replace a column's rule. Commas mean AND; repeat --when for OR. Prefix a fact with ! to negate it. Use --clear instead of --when for manual placement only. Inspect the confirmation's rules and affected cards before repeating it with its token. New custom columns start manual only; put a custom column before broader matching columns when it should win.
Facts:
worker:none,worker:working,worker:checks,worker:blocked,worker:hydra,worker:paused,worker:ended;owner-question,held,reminder-due,queued(queued behind a worker),done;pr:none,pr:draft,pr:open,pr:pending,pr:green,pr:red,pr:merged,pr:closed;kind:build,kind:investigation.
Pull request facts can coexist, including facts from different linked pull requests. Green and red require recorded checks; an absent summary is neither. Keep Needs you for real owner questions and reminders, and keep held work in Backlog. Exclude those facts when writing a broader custom rule:
pnyx-axi column rule custom:research --when "kind:investigation,!done,!held,!owner-question,!reminder-due" --reason "Keep investigations together" --hydra <hydra>column create --title "<name>" --description "<when and why>",column rename <id> --title "<name>"andcolumn describe <id> --description "<when and why>"maintain the columns.column reorder <id> --before <id>moves a column;column delete <id> --to <remaining-id>deletes it and places its cards in the destination. A Firstmate-linked Hydra's default columns cannot be deleted.- Card moves, column reorders, rule edits and deletes first return
confirmation: neededand a token: inspect the action and repeat the exact command with--confirm <token>. A changed target needs a new confirmation. column resize <id> --width <pixels>andhydra resize --width <pixels>change widths;layout showreports them and their defaults, andlayout resetrestores the default widths.
Pass --hydra <hydra> and --reason "<why>" on each.
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
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.

