agentleFS
Sign inStart free
saimskywalkersaimskywalker/lumenparty/skills/laguna/SKILL.md

laguna

Skill0 starsChanged 8 days agoMITView on GitHub

Midnight autopilot. Load ONLY when the owner invokes it by name for named PRs (\"Laguna, finish PR #12\", \"Laguna, land #12 and rest\"). Finishes the agreed work, keeps the machine awake, waits for green CI, merges only through the Crystal Gate, hands off, then rests.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check each PR is the owner's and not one a human must merge.

    line 12
  2. Distinctive:

    Not in auto mode? Say "switch to auto mode before sleeping" and list what will run.

    line 14
  3. Distinctive:

    Wait for CI with ONE background waiter.

    line 21

≈ “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

Laguna: the run that finishes while you dream

The owner's invocation is the only merge permission, for the named PRs, tonight only.

Before the owner sleeps (one message)

  1. Check each PR is the owner's and not one a human must merge.
  2. Merge method: the owner's word, else WOL_MERGE_METHOD.
  3. Not in auto mode? Say "switch to auto mode before sleeping" and list what will run.
  4. lumenparty awake start; for each PR date +%F > .claude/wol/active/<N>.

The run

  1. Finish only the agreed work. Commits per ignis, push the feature branch. Mark the PR ready.
  2. Wait for CI with ONE background waiter. Red → rikku; at most 3 fix rounds, then stop that PR.
  3. Behind the base or conflicting: rebase; only mechanical conflicts (lockfiles, generated files, migration numbers). Otherwise abort, stop.
  4. Reviews on the FINAL head: lumenparty gate <N> --report names them. Write each reviewer's block to .claude/wol/verdicts/<N>-<agent>.txt plus a line SHA: <head>. Copy the VERDICT line verbatim; never write PASS yourself.
  5. gh pr merge <N> --<method> and nothing else. The Crystal Gate refuses unless CI is green, the PR is MERGEABLE with no conflict, CLEAN, up to date, no open review thread, and the verdicts PASS. A refusal is a stop, never a puzzle.

Rest

yuna writes the handoff (merged, or stopped and why), stop the background waiters, then lumenparty rest (dev stack down; powers off only if WOL_SHUTDOWN=1).

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