fixflow

仓库创建 2025年12月9日最近提交 9 天前SkillHot 收录 20 天前

▸ 精选理由

适合需要可审计、可回溯交付的工程场景，助力稳健交付与持续集成。

这个 Skill 做什么

以严格步骤、持续测试与默认每步提交的策略来执行编码与交付工作流。

把编码交付当成流水线来做：先把整体计划定好，然后严格按步实现、每步跑测试并默认提交（per_step），必要时支持只在最后提交或按里程碑提交。适合执行需要高可靠性、可追踪变更的开发任务，也能在需求模糊时加入 BDD（Given/When/Then）。特点是强制性流程、持续验证，能显著降低回滚和误差。

▸ 展开 SKILL.md 英文原文

Use when executing coding tasks with a strict delivery workflow: build a full plan, implement one step at a time, run tests continuously, and commit by default after each step (`per_step`). Support explicit commit policy overrides (`final_only`, `milestone`) and optional BDD (Given/When/Then) when users ask for behavior-driven delivery or requirements are unclear.

Skill 开发管理交付流程持续验证提交策略通用

239

Stars

Forks

仓库内 Skill

7 日增星

安装 / 使用

给你的 Agent 一句话（通用）

帮我安装这个 skill：https://raw.githubusercontent.com/majiayu000/spellbook/main/skills/fixflow/SKILL.md

或 curl 直取 SKILL.md

curl -fsSL "https://raw.githubusercontent.com/majiayu000/spellbook/main/skills/fixflow/SKILL.md"

SKILL.MD 节选查看完整文件 ↗

# Fixflow

## Overview

Use this skill to deliver end-to-end engineering work in one run:
- Plan fully.
- Execute in strict sequence.
- Validate continuously.
- Use explicit commit policy (`per_step` default; `final_only`/`milestone` when requested).
- Add BDD behavior specs when requested or when requirements are ambiguous.

## Trigger Cues

Trigger this skill when the user asks for one or more of:
- Full plan + sequential execution.
- No backward compatibility.
- Test everything before handoff.
- Commit after completion or commit before each next step.
- Behavior-driven delivery (BDD) or acceptance scenarios.

## Workflow

### 1. Define Ready Criteria (DoR)

> See shared delivery base: [`r

via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有