agentleFS
Sign inStart free
Golden-PromiseGolden-Promise/codex-skill-library/skills/skill-phase-gate/SKILL.md

skill-phase-gate

Skill1 starsChanged 8 months agoMITView on GitHub

Use when a meaningful coding checkpoint is needed before or after risky execution, such as a multi-file refactor, migration, or pre-commit pause.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use skill-phase-gate to add an optional operational checkpoint around meaningful coding work.

    line 10

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

Skill Phase Gate

Overview

Use skill-phase-gate to add an optional operational checkpoint around meaningful coding work. It is for risky edits before or after execution, not for root-state refresh, packet compression, suite bootstrap, generic planning, or final handoff writing.

Use This Skill When

  • you are about to start a refactor, migration, or multi-file change and want a brief preflight gate
  • you have finished a meaningful edit and need a postflight checkpoint before commit or handoff
  • the task is risky enough that expected files, explicit non-goals, and a verification plan should be stated out loud
  • you want a pre-commit checkpoint for work that is substantial enough to deserve one more deliberate review pass

Do Not Use This Skill When

  • the request is a typo fix, tiny one-line edit, or similarly trivial change
  • the user only wants an explanation, walkthrough, or analysis with no checkpoint artifact
  • the main need is reconstructing current task state or preserving long-running state ownership
  • the main need is packet compression for the next live turn
  • the main need is suite bootstrap or routing
  • the main need is generating a full transfer packet or final handoff summary

Meaningful Checkpoint Bar

This package is a good fit when the checkpoint serves a meaningful workflow boundary:

  • good fit: refactors, multi-file changes, risky edits, migration checkpoints, or pre-commit review passes
  • bad fit: typo fixes, tiny one-line changes, pure explanation tasks, or generic up-front planning

Package Boundary

  • skill-phase-gate can mention current task state only to support the immediate checkpoint
  • skill-context-keeper remains the owner of root-state refresh and compression
  • skill-subtask-context remains the owner of local child-task state
  • skill-context-packet remains the owner of packet-sized next-turn context
  • this package does not replace suite bootstrap, planning packages, or handoff generation

References

  • README.md and README.zh-CN.md: install guidance, trigger boundaries, and non-goals
  • assets/PREFLIGHT.template.md: compact pre-execution gate
  • assets/POSTFLIGHT.template.md: compact post-execution gate
  • references/use-cases.md and references/use-cases.zh-CN.md: reader-facing positive and negative examples
  • references/prompt-templates.en.md and references/prompt-templates.zh-CN.md: ready-to-paste prompt patterns

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