save-progress — for Claude Code save-progress, metadev-protocol, community, for Claude Code, ide skills, The script runs, git add, git commit, "ok": true, skip-tests

v1.0.0

Об этом навыке

Подходящий сценарий: Ideal for AI agents that need you are in save-progress mode. run the deterministic preflight, then update project context. Локализованное описание: A high-performance Vibe Coding protocol based on the strict separation between Project Deliverables and Development Context. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

Возможности

You are in SAVE-PROGRESS mode. Run the deterministic preflight, then update project context.
DO NOT create a commit — that is a separate action.
If preflight fails, STOP and report — do not update .meta/ files.
Step 1 — preflight (deterministic, one command)
uv run python scripts/save progress preflight.py

# Core Topics

Vincent-20-100 Vincent-20-100
[0]
[0]
Updated: 4/21/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 8/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution
Review Score
8/11
Quality Score
46
Canonical Locale
en
Detected Body Locale
en

Подходящий сценарий: Ideal for AI agents that need you are in save-progress mode. run the deterministic preflight, then update project context. Локализованное описание: A high-performance Vibe Coding protocol based on the strict separation between Project Deliverables and Development Context. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

Зачем использовать этот навык

Рекомендация: save-progress helps agents you are in save-progress mode. run the deterministic preflight, then update project context. A high-performance Vibe Coding protocol based on the strict separation between

Подходит лучше всего

Подходящий сценарий: Ideal for AI agents that need you are in save-progress mode. run the deterministic preflight, then update project context.

Реализуемые кейсы использования for save-progress

Сценарий использования: Applying You are in SAVE-PROGRESS mode. Run the deterministic preflight, then update project context
Сценарий использования: Applying DO NOT create a commit — that is a separate action
Сценарий использования: Applying If preflight fails, STOP and report — do not update .meta/ files

! Безопасность и ограничения

  • Ограничение: DO NOT create a commit — that is a separate action.
  • Ограничение: If preflight fails, STOP and report — do not update .meta/ files.
  • Ограничение: Step 2 — narrative update (LLM, only if step 1 is green)

Why this page is reference-only

  • - Current locale does not satisfy the locale-governance contract.
  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is save-progress?

Подходящий сценарий: Ideal for AI agents that need you are in save-progress mode. run the deterministic preflight, then update project context. Локализованное описание: A high-performance Vibe Coding protocol based on the strict separation between Project Deliverables and Development Context. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

How do I install save-progress?

Run the command: npx killer-skills add Vincent-20-100/metadev-protocol/save-progress. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for save-progress?

Key use cases include: Сценарий использования: Applying You are in SAVE-PROGRESS mode. Run the deterministic preflight, then update project context, Сценарий использования: Applying DO NOT create a commit — that is a separate action, Сценарий использования: Applying If preflight fails, STOP and report — do not update .meta/ files.

Which IDEs are compatible with save-progress?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for save-progress?

Ограничение: DO NOT create a commit — that is a separate action.. Ограничение: If preflight fails, STOP and report — do not update .meta/ files.. Ограничение: Step 2 — narrative update (LLM, only if step 1 is green).

How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add Vincent-20-100/metadev-protocol/save-progress. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use save-progress immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

save-progress

A high-performance Vibe Coding protocol based on the strict separation between Project Deliverables and Development Context. This AI agent skill supports

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

You are in SAVE-PROGRESS mode. Run the deterministic preflight, then update project context.

Hard rules

  • DO NOT create a commit — that is a separate action.
  • If preflight fails, STOP and report — do not update .meta/ files.

Step 1 — preflight (deterministic, one command)

bash
1uv run python scripts/save_progress_preflight.py

The script runs: pytest, ruff check, ruff format --check, git status, and a check for stray drafts at the project root or code in .meta/scratch/. It prints a JSON summary and exits non-zero on any failure.

Step 2 — narrative update (LLM, only if step 1 is green)

  1. Update .meta/PILOT.md — status table reflects actual state, not aspirational. Mark completed items. Add new next steps.
  2. Rewrite .meta/SESSION-CONTEXT.md — architecture snapshot, active decisions (why), traps to avoid (what broke or could break), open questions. Rewrite, don't append.
  3. Report: "Ready to commit. Run git add and git commit."

Verification

  • Preflight JSON shows "ok": true for all 5 checks
  • PILOT.md reflects actual state
  • SESSION-CONTEXT.md captures traps and open questions, not just wins

Quick-pause mode (--skip-tests)

For mid-session checkpoints where tests are genuinely WIP, you may skip the pytest run:

bash
1uv run python scripts/save_progress_preflight.py --skip-tests

When to use: only when tests are intentionally red (e.g., mid-refactor, scaffold not yet wired). Not for "tests are slow" or "I can't fix this now."

Required: when using --skip-tests, add a Skip-Tests: true trailer to the commit message so the bypass is machine-readable in git history:

fix: partial scaffold for new module

Skip-Tests: true

Also note in SESSION-CONTEXT.md under "Traps to avoid" that tests are red and why, so the next session does not ship without fixing them.

Rationalizations you must not accept

ExcuseWhy it's wrong
"Tests are passing, that's enough."Lint and format issues compound — preflight catches them.
"I'll update PILOT.md later."You won't. Next session reads PILOT.md first; stale = wrong.
"SESSION-CONTEXT.md is fine from last time."Context decays every session. Rewrite, don't append.
"Small change, skip the preflight."Small changes break things. The script takes 30 seconds.
"Tests are slow, I'll use --skip-tests."--skip-tests is for intentionally red tests, not slow ones.

Связанные навыки

Looking for an alternative to save-progress or another community skill for your workflow? Explore these related open-source skills.

Показать все

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

widget-generator

Logo of f
f

Создание настраиваемых плагинов виджетов для системы ленты новостей prompts.chat

flags

Logo of vercel
vercel

Фреймворк React

138.4k
0
Браузер

pr-review

Logo of pytorch
pytorch

Tensors and Dynamic neural networks in Python with strong GPU acceleration

98.6k
0
Разработчик