Agent skill

Stack Create

Initializes a stacked branch set from an ordered plan, one branch per slice with parent-child links.

MITAuto-check passedDevelopment

Install Stack Create

skills CLI

$ npx skills add athola/claude-night-market --skill stack-create -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install athola/claude-night-market stack-create --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/athola/claude-night-market.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/sanctum/skills/stack-create .claude/skills/stack-create && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "stack-create" agent skill from https://github.com/athola/claude-night-market/tree/master/plugins/sanctum/skills/stack-create into .claude/skills/stack-create/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stack-create", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/athola/claude-night-market/tree/master/plugins/sanctum/skills/stack-create

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add athola/claude-night-market --skill stack-create -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install athola/claude-night-market stack-create --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/athola/claude-night-market.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/sanctum/skills/stack-create .agents/skills/stack-create && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "stack-create" agent skill from https://github.com/athola/claude-night-market/tree/master/plugins/sanctum/skills/stack-create into .agents/skills/stack-create/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stack-create", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add athola/claude-night-market --skill stack-create -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install athola/claude-night-market stack-create --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/athola/claude-night-market.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/sanctum/skills/stack-create .cursor/skills/stack-create && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "stack-create" agent skill from https://github.com/athola/claude-night-market/tree/master/plugins/sanctum/skills/stack-create into .cursor/skills/stack-create/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stack-create", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/athola/claude-night-market.git --path plugins/sanctum/skills/stack-create

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add athola/claude-night-market --skill stack-create -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install athola/claude-night-market stack-create --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/athola/claude-night-market.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/sanctum/skills/stack-create .gemini/skills/stack-create && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "stack-create" agent skill from https://github.com/athola/claude-night-market/tree/master/plugins/sanctum/skills/stack-create into .gemini/skills/stack-create/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stack-create", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install athola/claude-night-market stack-create

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add athola/claude-night-market --skill stack-create -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/athola/claude-night-market.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/sanctum/skills/stack-create .github/skills/stack-create && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "stack-create" agent skill from https://github.com/athola/claude-night-market/tree/master/plugins/sanctum/skills/stack-create into .github/skills/stack-create/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stack-create", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add athola/claude-night-market --skill stack-create -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install athola/claude-night-market stack-create --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/athola/claude-night-market.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/sanctum/skills/stack-create .opencode/skills/stack-create && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "stack-create" agent skill from https://github.com/athola/claude-night-market/tree/master/plugins/sanctum/skills/stack-create into .opencode/skills/stack-create/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stack-create", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: stack-create
GitHub stars: 342
Token cost: ~1.1k tokens
SKILL.md length: 429 words
Files: 1
Skills in repo: 160
Repo updated: Oct 6, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Initializes a stacked branch set from an ordered plan, one branch per slice with parent-child links.

Works in 4 steps: Verify Git Version (git-version-checked) → Identify Slices (slices-identified) → Create Branches (branches-created) → …
A plan has 2+ sequentially dependent changes
SKILL.md covers When To Use, When NOT To Use, Prerequisites and Required Progress Tracking, plus 6 more sections
Calls git

What it does

Stack Create is an agent skill from athola/claude-night-market. Initializes a stacked branch set from an ordered plan, one branch per slice with parent-child links. Use when a plan has 2+ sequentially dependent changes.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Git workflow. It works with Git. The repository describes itself as: 23 Claude Code plugins: TDD enforcement hooks, git/PR workflows, spec-driven development, code review, project lifecycle, fix-from-error, maintenance automation, context… The licence is MIT.

When your agent uses it

A plan has 2+ sequentially dependent changes
Tasks that involve Git workflow

Example prompts

“Use the stack-create skill to initializ a stacked branch set from an ordered plan, one branch per slice with parent-child links”
“/stack-create”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

Verify Git Version (git-version-checked)
Identify Slices (slices-identified)
Create Branches (branches-created)
Verify Stack (stack-verified)

What it can do on your machine

Read from SKILL.md and the folder at commit 9f3eb00. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Stack Create loads about 1.1k tokens when it runs. Until then it costs about 42 tokens; SKILL.md has 429 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~42
When it runs · the whole SKILL.md, loaded when a task matches: ~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from athola/claude-night-market at commit 9f3eb00, republished under its MIT licence (© athola). 429 words, ~1,135 tokens.

Download SKILL.mdSave it as .claude/skills/stack-create/SKILL.md (or your agent's skills folder).

name: stack-create
description: Initializes a stacked branch set from an ordered plan, one branch per slice with parent-child links. Use when a plan has 2+ sequentially dependent changes.
alwaysApply: false
category: workflow-automation
tags: git, stacked-diffs, pr, branches, planning
complexity: medium
model_hint: standard
estimated_tokens: 800
dependencies: sanctum:git-workspace-review, sanctum:do-issue

Stack Create

Initialize a stacked branch set from a multi-step plan. Each logical slice of the plan becomes one branch targeting the previous slice's branch as its base.

When To Use

Use stack-create when a plan produces 2 or more ordered changes where each change depends on the previous one completing (and merging) before it can land. For independent changes, use parallel worktrees instead (see egregore).

When NOT To Use

A single independent change, which should branch normally instead
The stack exists and needs publishing (use sanctum:stack-push)

Prerequisites

Git 2.38+ (git version | awk '{print $3}' to check)
gh CLI authenticated
A written plan with ordered slices (from do-issue or attune:blueprint)
Clean working tree on the base branch (git status)

Required Progress Tracking

Create TodoWrite items before starting:

stack-create:git-version-checked
stack-create:slices-identified
stack-create:branches-created
stack-create:stack-verified

Step 1: Verify Git Version (`git-version-checked`)

bash

git version

Confirm the output is 2.38.0 or higher. If not, the --update-refs flag is unavailable. Warn the user and fall back to manual branch tracking.

Check for optional jj accelerator:

bash

if command -v jj &>/dev/null && jj root &>/dev/null 2>&1; then
  echo "jj available"
else
  echo "using git --update-refs"
fi

Step 2: Identify Slices (`slices-identified`)

Read the plan and extract ordered slices. Each slice must satisfy:

A single logical concern (one PR worth of change)
A clear dependency on the slice before it (if any)
A short name suitable for a branch suffix

Example slices for a plan with three parts:

Slice 1: add-schema     -- database schema changes
Slice 2: add-api        -- API layer (depends on schema)
Slice 3: add-ui         -- frontend (depends on API)

Record the slice list before creating branches.

Step 3: Create Branches (`branches-created`)

Starting from the base branch (usually master or main):

bash

BASE=master
STACK=stack/my-feature

# Slice 1 branches from master
git checkout -b ${STACK}/add-schema ${BASE}

# Slice 2 branches from slice 1
git checkout -b ${STACK}/add-api ${STACK}/add-schema

# Slice 3 branches from slice 2
git checkout -b ${STACK}/add-ui ${STACK}/add-api

Convention: stack/<feature-name>/<slice-name>

Return to the first slice branch to begin work:

bash

git checkout ${STACK}/add-schema

jj Accelerator (if available)

bash

# jj creates an empty commit on each branch automatically
# Use jj new to move to a new change
jj new -m "stack: add-schema" --no-edit

Show full SKILL.md (172 more words)Show less

Step 4: Verify Stack (`stack-verified`)

Confirm the branch topology is correct:

bash

git log --oneline --graph \
  ${BASE}..${STACK}/add-ui

Each slice branch should appear as a linear chain above the base.

If jj is available:

bash

jj log --revisions \
  "ancestors(${STACK}/add-ui, 10) & !ancestors(${BASE})"

Notes

Never push branches until at least one commit exists on each slice (empty branches produce confusing PRs)
The slice name in the branch becomes the PR title prefix by convention; keep it short and descriptive
After creating the stack, proceed to stack-push to open PRs, or work slice-by-slice and push when ready
If the plan changes, add or remove branches manually and re-verify the topology in Step 4

Exit Criteria

All 4 TodoWrite items (stack-create:git-version-checked through stack-create:stack-verified) are created before branch creation starts and marked complete in order
Git version confirmed ≥ 2.38.0; if not, fallback to manual branch tracking is documented and the user is warned
All slice branches created with the naming convention stack/<feature-name>/<slice-name>
git log --oneline --graph <base>..<tip> shows a linear chain with each slice branch appearing in dependency order
Working tree returned to the first slice branch after topology is verified

Files

Just SKILL.md in plugins/sanctum/skills/stack-create of athola/claude-night-market.

Open the folder on GitHubat commit 9f3eb00

Compare with similar skills

Stack Create next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Stack Create compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Stack Create this skillathola/claude-night-market	342	—	~1.1k	Automated safety check: Pass	MIT	yesterday
Finishing a Development Branchobra/superpowers	296k	5 repos	~1.9k	Automated safety check: Pass	MIT	yesterday
Code Design Rationale Investigatorcursor/plugins	10k	9 repos	~2.6k	Automated safety check: Pass	None	yesterday
Contributor-First PR MergeHKUDS/OpenHarness	16k	1 repos	~847	Automated safety check: Pass	MIT	4 mo ago
Migrate Internal Package into GhostTryGhost/Ghost	55k	—	~3.8k	Automated safety check: Pass	MIT	yesterday
Create Pull Requestcline/cline	70k	1 repos	~1.6k	Automated safety check: Pass	Apache-2.0	yesterday

Similar skills

Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
296k GitHub starsUsed in 5 repos~1.9k tokens
DevelopmentAuto-check passed
Code Design Rationale Investigator
cursor/plugins
Official
Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.
10k GitHub starsUsed in 9 repos~2.6k tokens
DevelopmentAuto-check passed
Contributor-First PR Merge
HKUDS/OpenHarness
Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.
16k GitHub starsUsed in 1 repo~847 tokens
DevelopmentAuto-check passed
Migrate Internal Package into Ghost
TryGhost/Ghost
Moves a package from another TryGhost repository into Ghost as an internal workspace package while keeping its Git history, with checkpoints for the steps that need an administrator.
55k GitHub stars~3.8k tokensUpdated yesterday
DevelopmentAuto-check passed
Create Pull Request
cline/cline
Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.
70k GitHub starsUsed in 1 repo~1.6k tokens
DevelopmentAuto-check passed
Git Merge Conflict Resolver
tailcallhq/forgecode
Resolves Git merge conflicts with a plan-first workflow that keeps both sides' intent, regenerates lock files and backs up deleted-but-modified files.
7.6k GitHub starsUsed in 1 repo~4.5k tokens
DevelopmentAuto-check passed

Questions about Stack Create

What does Stack Create do?

Initializes a stacked branch set from an ordered plan, one branch per slice with parent-child links. Stack Create is an agent skill from athola/claude-night-market. Initializes a stacked branch set from an ordered plan, one branch per slice with parent-child links.

When should I use Stack Create?

Stack Create fits situations like: A plan has 2+ sequentially dependent changes; tasks that involve Git workflow.

How do I install Stack Create in Claude Code?

Run `npx skills add athola/claude-night-market --skill stack-create -a claude-code`. Or copy the skill folder (plugins/sanctum/skills/stack-create in athola/claude-night-market) into .claude/skills/stack-create in your project. Claude Code loads it when a task matches its description.

How do I install Stack Create in Codex?

Run `npx skills add athola/claude-night-market --skill stack-create -a codex`. Or copy the skill folder (plugins/sanctum/skills/stack-create in athola/claude-night-market) into .agents/skills/stack-create in your project. Codex loads it when a task matches its description.

Can I use Stack Create in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add athola/claude-night-market --skill stack-create -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/stack-create, .gemini/skills/stack-create, .github/skills/stack-create and .opencode/skills/stack-create in your project.

What does Stack Create need to run?

Going by SKILL.md and its folder, Stack Create needs the command-line tools its instructions call (git).

Does Stack Create access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Stack Create safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Stack Create use?

Stack Create is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Stack Create use?

About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Stack Create?

Skills that share tags, products or a category with Stack Create: Finishing a Development Branch (obra/superpowers, 296k stars), Code Design Rationale Investigator (cursor/plugins, 10k stars), Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars) and Migrate Internal Package into Ghost (TryGhost/Ghost, 55k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Stack Create?

athola (a GitHub user) maintains it in athola/claude-night-market, which has 342 GitHub stars. The repository holds 160 skills in this directory. The repository was last updated on October 6, 2026.

Source: athola/claude-night-market on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Stack Create

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Stack Create

When To Use

When NOT To Use

Prerequisites

Required Progress Tracking

Step 1: Verify Git Version (git-version-checked)

Step 2: Identify Slices (slices-identified)

Step 3: Create Branches (branches-created)

jj Accelerator (if available)

Step 4: Verify Stack (stack-verified)

Notes

Exit Criteria

Files

Compare with similar skills

Similar skills

More from athola/claude-night-market

Related

Questions about Stack Create

Step 1: Verify Git Version (`git-version-checked`)

Step 2: Identify Slices (`slices-identified`)

Step 3: Create Branches (`branches-created`)

Step 4: Verify Stack (`stack-verified`)