메뉴
Use when you need to run tests or formatters across every commit in a stack. Use INSTEAD of manual git test run or looping git checkout + test. Prevents: untested commits, wrong parallelism settings, cache misunderstandings.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
Use when you need to fix, correct, or update content in an earlier commit. Absorbs staged changes into correct stack commits INSTEAD of running git absorb or git commit --fixup via Bash. Prevents: missed dry-run preview, leftover staged changes going unnoticed, forgetting to restack. Falls back to guided manual amend when absorb cannot route hunks.
Use when you need to plan commits, restructure a stack, or commit uncommitted work as organized atomic commits. Builds a stack from a description, uncommitted work, or existing commits INSTEAD of manual git rebase -i, git reset --soft, or ad-hoc git move sequences. Prevents: wrong commit ordering, forward references, git move -F panics, untested intermediates.
Use when you need to break up, split, or decompose a large commit into smaller atomic commits. Use INSTEAD of manual git rebase -i + edit or git reset HEAD^. Prevents: non-working intermediate commits, wrong split ordering, missed downstream restack.
Use when you need to push, submit, or create pull requests for a commit stack. Syncs, validates, and pushes INSTEAD of manual git sync + git submit + PR/MR creation. Handles branch creation, stacked PR/MR creation with correct base branches.
Use when you need to audit, analyze, or review stack quality before restructuring. Produces a structured summary with per-commit classification, philosophy audit, and violation flags. Output feeds directly into /stack-plan restructure mode. Use INSTEAD of manual git log inspection.
SOC 직업 분류 기준
| name | stack-test |
| description | Use when you need to run tests or formatters across every commit in a stack. Use INSTEAD of manual git test run or looping git checkout + test. Prevents: untested commits, wrong parallelism settings, cache misunderstandings. |
| argument-hint | <command> [--fix] [--jobs N] [revset] |
| disable-model-invocation | false |
| compatibility | Requires git-branchless |
Run a test command or formatter across commits in the current stack.
Load references — read references/git-branchless.md (relative to this
skill's directory) before proceeding.
Check branchless init:
if [ ! -d ".git/branchless" ]; then git branchless init; fi
--fix: use fix mode (apply changes per commit, e.g., formatters)--jobs N: parallelism level (0 = auto-detect CPUs)stack())Parse $ARGUMENTS. If no command is provided, detect from the project:
package.json → npm test or pnpm testCargo.toml → cargo testMakefile → make testflake.nix → nix flake checkDetermine mode. If --fix is in arguments, use fix mode. Otherwise
use run mode.
Determine target revset. If a revset argument is provided, use it.
Otherwise default to stack().
Run tests across the stack:
git test run -x '<command>' '<revset>'
Add --jobs <N> if specified (uses worktree strategy automatically).
Default to --jobs 0 for parallel when the project supports it.
Report results:
git test run -x '<command>' --search binary to bisect if the
failure pattern is unclearApply formatter across the stack:
git test fix -x '<command>' '<revset>'
Add --jobs 0 for parallel execution. Fix mode replaces tree OIDs directly
and never produces merge conflicts.
Verify with git sl to show any commits that were modified.
Optionally re-run tests to confirm the formatting didn't break anything:
git test run -x '<test-command>' '<revset>'
/stack-test "npm test"
/stack-test "cargo fmt --all" --fix
/stack-test "prettier --write ." --fix --jobs 0
/stack-test "make lint" stack()
/stack-test "npm test" --jobs 4 draft()
git test clean to clear.
Use --no-cache to bypass the cache for the current run without clearing
stored results (useful after environment changes).--jobs >1 implies worktree strategy (concurrent git worktrees).BRANCHLESS_TEST_COMMIT env var is available inside the test command.