Menu

Individual skill

principle-sequence-verifiable-units

Apply to bulk sweeps, migrations, repeated near-identical edits, and stacks of commits or PRs. Break the job into slices, each closed by a check that passes, and order commits so that reading the history shows a reviewer the change is correct.

plugins/requie/endostack/skills/principle-sequence-verifiable-units/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,531
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Build in checkable steps

Split work that takes several steps into small units. Each unit ends with something a check can confirm, and you confirm it before starting on the next one. Order the commits and PRs so a reviewer reading them in sequence can see that the change is correct.

## When it applies

Large sweeps, migrations, batches of similar edits, and choices about stacking commits and PRs. One atomic change does not need it.

## What to do

Execution:

1. Rebase onto a clean trunk first, so every check compares against the true baseline.
2. Treat each unit as a bracket: start from a known-good state, make one change, run the check, and continue only if it passes. When upgrading a vulnerable dependency across twelve services, upgrade one service, run its tests, then move to the next. A failure then points at exactly one service.