agentleFS
Sign inStart free
revealui-studiorevealui-studio/revskills/skills/revealui-rollup/SKILL.md

revealui-rollup

Skill2 starsChanged 40 days agoMITView on GitHub

One-off MASTER_HANDOFF regen. Alias /rollup. Runs the GAP-314 master-handoff-regen workflow (report-first sweep + regen brief; agent reviews then commits). Use when MASTER_HANDOFF is STALE or EXPIRED, or the user asks to roll up handoffs. Never auto-run from /checkpoint. Not /checkpoint. Not /cleanup.

  • Commits and pushes

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 1 is distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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. Distinctive:

    Read the printed consolidation brief.

    line 40
  2. Very specific:

    If a sweep moved files or a regen is required, commit only what the script changed, on a chore/ branch from origin/test, fragments/derived …

    line 41
  3. Very specific:

    Do not run this from /checkpoint (expensive, owner-attended).

    line 53
  4. Very specific:

    Do not call master-handoff-regen.js from a hook.

    line 54
  5. Very specific:

    Do not commit CURRENT-HANDOFF.md as part of a rollup unless the script's own contract says so (it does not — rolling fragments stay the …

    line 55
  6. Very specific:

    Do not treat this as /cleanup (session residue) or /checkpoint (session handoff).

    line 56

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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

Rollup (/rollup) — MASTER_HANDOFF regen

Thin one-off onto the registered workflow master-handoff-regen ($JV_REPO/workflows/master-handoff-regen.yml). Delegates to workflow-run.js. Report-first: the script may sweep aged dated handoffs and print a regen brief; it does not silently rewrite the master body. Agent reviews, then commits on a .jv feature branch if a delta landed.

Load helpers:

. "$REVEALFLEET_ROOT/revskills/scripts/lib/session-state.sh"

Run

node "$JV_REPO/scripts/workflow-run.js" master-handoff-regen

--dry-run on the runner prints the plan. The underlying script also accepts --dry-run / --sweep-only / --apply-frontmatter via its own CLI (Tier 2 escape hatch) — this skill stays on the named workflow.

After the brief

  1. Read the printed consolidation brief.
  2. If a sweep moved files or a regen is required, commit only what the script changed, on a chore/ branch from origin/test, fragments/derived per .jv coord rules.
  3. gh pr create --base test with label merge:merge-commit. Do not self-merge.

Where this is wired

SurfaceHow
/checkpoint Step 2cIf staleness is STALE or EXPIRED, list /rollup under OUTSTANDING. Do not run it inside checkpoint.
/ops master-handoff-regenSame workflow by name

Do not

  • Do not run this from /checkpoint (expensive, owner-attended).
  • Do not call master-handoff-regen.js from a hook.
  • Do not commit CURRENT-HANDOFF.md as part of a rollup unless the script's own contract says so (it does not — rolling fragments stay the write surface).
  • Do not treat this as /cleanup (session residue) or /checkpoint (session handoff).

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.

Reviews can't be read right now.

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