刷新队列
安装方式
先用 Prompt 核对来源,也可切换到安装命令或下载可用的安装包。
用 AI 助手安装
复制提示词,让助手先核对固定版本和依赖。
查看 Prompt收起 Prompt
先检查当前 Agent 是否已安装 SkillPI Skill Finder。如果尚未安装,请按官方仓库的说明安装并启用:https://github.com/Findskills/skillpi。然后使用 Skill Finder 打开此 SkillPI 详情页并定位 "flush":https://skillpi.com/zh/skills/deepskill-b20509f5628a4e2ae96b0e697be53132a396de2b210cfaba719d5ae279b2f687。安装前核对上游来源和版本:https://github.com/jeremylongshore/tons-of-skills-marketplace/blob/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/hyperflow/skills/flush/SKILL.md。来源不一致时停止并说明差异。核对通过后,用 Skill Finder 安装目标 Skill,并报告安装路径和来源版本。
此命令从 GitHub 来源仓库获取指定技能。运行前请先查看源文件。
npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/hyperflow/skills/flush --skill flush来源与配置
查看 GitHub 源码jeremylongshore/tons-of-skills-marketplace固定提交 6ea46b08dce892944db7c16f28d0b5308d402402
配置方式待核实
请查看原始来源中的适用工具、依赖和权限要求。
安装实测待补充
本条目介绍 刷新队列 的公开用途。DeepSkill 当前公开目录说明:“当用户需要手动刷新之前或中断的链中的延迟提交队列时使用。读取 .hyperflow/commits-queue/manifest.json,将暂存分支快进到用户分支,删除暂存分支,并清空队列。在链在第 4 步自动刷新前崩溃时用于恢复。 触发命令:/hyperflow:flush、"flush pending commits"、"flush queue"、"apply staged commits"、"where are my commits"。” 适用场景包括Git 工作流。本页根据公开目录资料和固定版本的上游仓库整理,建议使用前核对该版本的环境、工具、权限及数据处理要求。Skillπ 提供站方用途介绍与原站链接;原始 SKILL.md 和附件仅在对应许可允许时开放。
文件浏览
--- name: flush description: | Use when the user wants to manually flush a deferred-commit queue from a prior or interrupted chain. Reads .hyperflow/commits-queue/manifest.json, fast-forwards the staging branch onto the user's branch, deletes staging, clears the queue. Recovery interface when a chain crashed before its Step 4 auto-flush ran. Trigger with /hyperflow:flush, "flush pending commits", "flush queue", "apply staged commits", "where are my commits". allowed-tools: Read, Bash(git:*), Bash(ls:*), Bash(cat:*), Bash(rm:*), Bash(bash:*), Bash(scripts/*:*) argument-hint: "[--dry-run]" version: 4.12.7 license: MIT compatibility: Designed for Claude Code tags: [git, deferred-commits, recovery, lifecycle] --- # 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.
当前收录版本
4.12.7
质量评测
满分 100。前四项来自 DeepSkill 收录的质量报告。
评分依据
解决链中断后延迟提交队列的手动刷新问题,具有明确的恢复场景价值
评分依据
触发命令明确列出多个变体,覆盖合理,边界清晰
评分依据
Phase/步骤清晰,有出口条件,含端到端示例,frontmatter 完整
评分依据
工具来源明确,参数正确,覆盖主要异常,不可逆操作有 dry-run 机制
计算方式
取前四项原始分值的算术平均,四舍五入取整。可通过收录报告核对各项评分与说明,运行记录需单独查证。
权限与使用前检查
根据当前主文档自动整理,命中内容可能是示例或防护说明;不是实际权限声明,也未覆盖附件、外部依赖或运行行为。
未从主文档识别到上述常见操作,不能据此判断无需权限或没有风险。
安全评级与访问范围
risk · 静态证据核验,不代表运行安全保证。
使用前请由宿主核对并授权实际文件读写、外部服务和联网目的地;本站的核验不会授予任何运行权限。
用户讨论
还没有已核实的点评。