stack-push
Pushes all branches in a stack and opens or updates one dependent PR per slice. Use after stack-create to publish the stack or after adding commits to a slice.
Install / Use
npx skills add athola/claude-night-market --skill stack-pushInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
AutomationSupported Platforms
Our assessment of stack-push
stack-push scores 86/100 on our quality scale, 1843rd of 2,771 Automation skills we index.
Its SKILL.md is 5.0 KB long, well organised into 13 sections with 6 code examples: a solid amount of guidance for an agent.
It has 338 GitHub stars, a meaningful sign that others use it.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so stack-push is actively maintained.
- Our last check on 2026-11-04 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-07. Automated pattern scan on 2026-10-07. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
stack-push compared with similar skills
All 4 of these similar skills score higher than stack-push; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| stack-push (this skill)by athola | 86 | 338 | 57d ago | SKILL.md |
| Agent-Reachby Panniantong | 100 | 113.3k | 12d ago | CLAUDE.md |
| rufloby ruvnet | 100 | 82.1k | today | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 40.2k | 10d ago | CLAUDE.md |
| Scraplingby D4Vinci | 100 | 104.4k | 2d ago | MCP Server |
Frequently asked questions
- How do I install stack-push?
- Run
npx skills add athola/claude-night-market --skill stack-push. The install tabs above show the steps for each supported agent. - Which AI agents does stack-push work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is stack-push safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is stack-push still maintained?
- The repository was last updated about 2 months ago, so stack-push is actively maintained.
Skill content
View source on GitHubname: stack-push description: Pushes all branches in a stack and opens or updates one dependent PR per slice. Use after stack-create to publish the stack or after adding commits to a slice. alwaysApply: false category: workflow-automation tags:
- git
- stacked-diffs
- pr
- push
- github tools: [] complexity: medium model_hint: standard estimated_tokens: 900 dependencies:
- sanctum:stack-create
- sanctum:pr-prep
- sanctum:git-workspace-review
Stack Push
Push all branches in a stack and open (or update) one PR per slice, with each PR targeting its parent branch as base.
When To Use
Run stack-push after stack-create has initialized the
branch topology and at least one commit exists on each
slice branch.
Also run it after adding commits to any slice to update
open PRs.
When NOT To Use
- No stack exists yet (use
sanctum:stack-create) - The base merged and the stack must catch up (use
sanctum:stack-rebase)
Prerequisites
stack-createcompleted: branches exist with commitsghCLI authenticated (gh auth status)- Each slice branch has at least one commit beyond its base
Required Progress Tracking
Create TodoWrite items before starting:
stack-push:branches-listedstack-push:branches-pushedstack-push:prs-openedstack-push:stack-summary-posted
Step 1: List Stack Branches (branches-listed)
Identify all branches in the stack.
By convention they share a stack/<feature-name>/ prefix:
STACK=stack/my-feature
BASE=master
git branch --list "${STACK}/*" | sed 's/^[* ]*//'
Verify each branch has commits beyond the base:
for branch in $(git branch --list "${STACK}/*" \
| sed 's/^[* ]*//'); do
count=$(git rev-list --count \
"$(git merge-base ${BASE} ${branch})..${branch}")
echo "${branch}: ${count} commit(s)"
done
Any branch showing 0 commits must have work added before
pushing.
Step 2: Push Branches (branches-pushed)
Push every slice branch to the remote in stack order (base slice first):
for branch in $(git branch --list "${STACK}/*" \
| sed 's/^[* ]*//' | sort); do
git push --set-upstream origin "${branch}"
echo "pushed: ${branch}"
done
jj Accelerator (if available)
jj git push --all
Step 3: Open or Update PRs (prs-opened)
Create one PR per slice, targeting its parent branch.
For the first slice the parent is master; for subsequent
slices the parent is the previous slice's branch.
PREV_BASE=master
for branch in $(git branch --list "${STACK}/*" \
| sed 's/^[* ]*//' | sort); do
# Check if a PR already exists for this branch
existing=$(gh pr list \
--head "${branch}" \
--json number \
--jq '.[0].number' 2>/dev/null)
if [ -n "${existing}" ]; then
echo "PR #${existing} already open for ${branch} -- skipping"
else
gh pr create \
--base "${PREV_BASE}" \
--head "${branch}" \
--title "[$(echo ${branch} | sed 's|.*/||')] <title>" \
--body "Part of stack \`${STACK}\`." \
--draft
echo "opened PR for ${branch} (base: ${PREV_BASE})"
fi
PREV_BASE="${branch}"
done
Fill in the actual PR titles and bodies before removing
the --draft flag.
Run Skill(sanctum:pr-prep) on each slice to generate
quality-gated descriptions.
Step 4: Post Stack Summary (stack-summary-posted)
After all PRs are open, post a summary comment on the first PR (the root of the stack) listing the full chain:
ROOT_PR=$(gh pr list \
--head "${STACK}/$(git branch --list \
"${STACK}/*" | sed 's/^[* ]*//' | sort | head -1 \
| sed 's|.*/||')" \
--json number --jq '.[0].number')
# Build the stack table
BODY="## Stack\n\n| # | Branch | PR |\n|---|--------|----|\n"
N=1
for branch in $(git branch --list "${STACK}/*" \
| sed 's/^[* ]*//' | sort); do
pr_num=$(gh pr list --head "${branch}" \
--json number --jq '.[0].number')
BODY="${BODY}| ${N} | \`${branch}\` | #${pr_num} |\n"
N=$((N+1))
done
gh pr comment "${ROOT_PR}" --body "$(printf "${BODY}")"
Notes
- Always push in stack order so GitHub sees the parent branch before the child PR is opened
- Use
--draftby default; promote slices to ready individually as they pass review - After any
git rebase --update-refsrun, re-push withgit push --force-with-lease(never--force) - When a base PR merges, run
Skill(sanctum:stack-rebase)to cascade the rebase before updating the next PR's base
Exit Criteria
- [ ] All 4 TodoWrite items (
stack-push:branches-listedthroughstack-push:stack-summary-posted) are created before pushing starts and marked complete in order - [ ] Each slice branch confirmed to have ≥ 1 commit beyond its base
before
git pushis called; branches with 0 commits are blocked - [ ] One draft PR opened per slice, each targeting its parent branch
as base (root slice targets
master/main) - [ ] Root PR receives a
## Stackcomment containing a table with columns#,Branch, andPRlisting all slices - [ ]
gh pr list --head <branch>returns a PR number for each pushed branch after the step completes
Related Skills
Agent-Reach
113.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ruflo
82.1k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
Claude-Code-Game-Studios
40.2kTurn Claude Code into a full game dev studio — 49 AI agents, 75 workflow skills, and a complete coordination system mirroring real studio hierarchy.
Scrapling
104.4k🕷️ The BEST Web Scraping framework that handles everything from a single request to a full-scale crawl! Don't be shy, join here: https://discord.gg/EMgGbDceNQ and follow here for daily tips and tricks: https://x.com/Scrapling_dev
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
