git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace /tmp/flush && cp -r /tmp/flush/plugins/ai-agency/hyperflow/skills/flush ~/.claude/skills/flushSKILL.md
# Flush Manually flush the deferred-commit queue from a chain that ran with `commit-when=end`. Normally `/hyperflow:dispatch` calls `scripts/flush-commits.sh` at its Step 4 wrap-up; this skill exists for the case where the chain was interrupted (crash, kill, context loss) before the auto-flush ran. ## Subcommands | Subcommand | Description | |---|---| | (no arg) | Run `scripts/flush-commits.sh <project-root>` — fast-forward staging onto user's branch, delete staging, clear queue | | `--dry-run` | Show what would be flushed without doing it. Lists the queued commits in order. | ## What gets flushed `.hyperflow/commits-queue/manifest.json` tracks the chain's `user_branch`, `staging_branch` (always `hyperflow/staging-<chain-id>`), and the list of queued commits with SHAs and messages. Flush replays them via `git merge --ff-only` so: - All N commits land on the user's branch with original SHAs preserved - Order is chronological (queue-time order) - Original commit messages are preserved - Original file-to-message mapping is preserved (each commit touched exactly the files its sub-task touched) ## What happens if fast-forward isn't possible If the user's branch diverged from staging (e.g. the user committed manually mid-chain on the same branch), `git merge --ff-only` refuses. The skill surfaces the error with two recovery options: 1. `git rebase hyperflow/staging-<chain-id>` — replay staging commits on top of user's new commits 2. `git cherry-pick <staging-base>..hyperflow/staging-<chain-id>` — selectively pick commits The staging branch is preserved for the user to act on manually. The queue manifest stays in place so a future `/hyperflow:flush` retry can attempt again after the user resolves divergence. ## Flow 1. Check `.hyperflow/commits-queue/manifest.json` exists. If not, print `No queue to flush.` and stop. 2. Run `bash $PLUGIN_ROOT/scripts/flush-commits.sh $PROJECT_ROOT [--dry-run]`. 3. Print the script's output verbatim. ## Overview `/hyperflow:flush` is the user-facing handle for the deferred-commit flush mechanism. Most users never call it explicitly — `/hyperflow:dispatch` Step 4 wrap-up runs the same script automatically. This skill exists for recovery: if a chain ran with `commit-when=end` and crashed before wrap-up, the queue persists on disk and the user can flush it later. ## Prerequisites - `.hyperflow/commits-queue/manifest.json` exists from a prior chain run with `commit-when=end`. - Git repository, on a branch the manifest's `user_branch` field can be checked out into. - `scripts/flush-commits.sh` available in the plugin install. ## Error Handling | Failure | Behavior | |---|---| | No manifest file present | Print `No queue to flush.` Exit 0. | | Staging branch missing (manual deletion or rename) | Print warning; clear stale manifest. Exit 0. | | Fast-forward not possible (user branch diverged) | Surface git error + recovery suggestions (rebase / cherry-pick). Leave staging branch + manifest intact for manual handling. Exit non-zero. | | User on a branch other than manifest's user_branch | Check out manifest's user_branch automatically; if checkout fails, surface error. | ## Examples ### Dry-run before flushing ``` /hyperflow:flush --dry-run flush-commits (DRY RUN): would fast-forward 7 commits from hyperflow/staging-2026-05-17-1430 onto feat/auth-refactor abc1234 feat(auth): T7 wire login handler def5678 feat(auth): T6 add session middleware … ``` ### Recovery after crash ``` You: /hyperflow:flush flush-commits: flushed 7 commits onto feat/auth-refactor abc1234 feat(auth): T7 wire login handler … ``` ## Resources - [`scripts/flush-commits.sh`](../../scripts/flush-commits.sh) — the actual flush mechanism. - [`scripts/queue-commit.sh`](../../scripts/queue-commit.sh) — the queue-write side called by dispatch during the chain. - [DOCTRINE.md Layer 8](../hyperflow/DOCTRINE.md#layer-8-git-workflow) — `commit-when` timing rules.
Guard the beads execution record: enforce the write-flush-verify discipline that defeats the bd rapid-write race, audit epic dependency graphs for cycles and orphans, catch closures whose title overstates what shipped, flag open beads carrying no disposition or a disproven premise, and reconcile bd against its GitHub and Plane projections. Owns RECORD INTEGRITY; delegates graph analysis to bead-dependency-mapper and epic-closure drift to bead-epic-auditor rather than duplicating them. Use before closing an epic, after any batch of bd writes, when a bead premise looks stale, or when auditing whether the record matches reality. Trigger with "audit beads", "check the bead DAG", "did that close actually land", "bead hygiene".
Verify every factual assertion in a diff, PR body, commit message, bead note, or governing doc against the actual repository, and fail anything that cannot be substantiated by a command. Use before merging any PR that makes claims about counts, coverage, consumers, enforcement, provenance, or certification, and when auditing standing docs for rot. Trigger with "verify claims", "check this PR body", "is this claim true", "claim audit".
Design and build Omarchy (Quickshell/QML) bar-widget, panel, and service plugins that actually work on a stock install. Knows the hard runtime constraint (no node on the graphical session PATH), the first-party contracts (BarWidget, Panel, KeyboardPanel, PanelKeyCatcher, Service), the curl-from-QML data pattern, FileView persistence, and the marketplace submission bar. Use when starting a new Omarchy plugin, porting a plugin off an external runtime, wiring a service to a bar widget, or deciding how a widget should fetch and persist. Trigger with "build an omarchy plugin", "omarchy widget", "quickshell plugin", "port this plugin to QML".
Audit an Omarchy plugin before it reaches the marketplace: prove it installs and runs on a stock box (no node/python on the session PATH), run the omarchy-submit gate lane, validate on the rig with omarchy-plugin-validate and qmllint, and check the QML security invariants and first-party idiom contracts. Read-only: it reports and blocks, it does not rewrite the plugin. Use before submitting an entry, after any data-layer change, or when a plugin works on the dev box and you need to know whether it works for a real user. Trigger with "audit this omarchy plugin", "is this plugin submission ready", "will this plugin work when installed".
Audit and fix Claude Code SKILL.md files against enterprise compliance standards: frontmatter completeness, required body sections, and style. Use when validating or repairing skills in a plugin directory. Trigger with "audit skill", "fix skill compliance".
Learn how SKILL.md files work in Claude Code plugins, then build a production-quality agent skill from scratch. Covers frontmatter schema, body structure, testing, and iteration.
Step-by-step guide to writing a SKILL.md file for Claude Code. Learn how to plan, structure, and test auto-activating skills with proper frontmatter, allowed-tools, dynamic context injection, and supporting files.
|