stack-branch — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited stack-branch (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Create a new branch based on an existing PR branch (not main) for dependent work.
/stack-branch AB-456
/stack-branch AB-456 feature/parent-branch # Explicit parentThe first argument is the Jira ticket number for the new work.
Use the /jira-ticket skill or the Jira MCP tools directly to get ticket details:
mcp__jira__jira_get with:
path: /rest/api/3/issue/{ticketNumber}
jq: "{key: key, summary: fields.summary, issuetype: fields.issuetype.name}"If parent branch not specified:
# Check if currently on a feature branch
git branch --show-currentIf on a feature branch (not main), offer to use it as the parent. Otherwise, ask the user which branch to stack on.
# Fetch the parent branch
git fetch origin {parent-branch}
# Check out and update local copy
git checkout {parent-branch}
git pull origin {parent-branch}Map the Jira issue type to conventional commit prefix:
| Issue Type | Prefix |
|---|---|
| Story | feat |
| Task | feat |
| Bug | fix |
| Improvement | feat |
| Spike | chore |
| Sub-task | inherit from parent |
Create branch name:
{prefix}/{TICKET}-{summary-in-kebab-case}Example: feat/AB-456-add-caching-layer
git checkout -b {new-branch-name}git push -u origin {new-branch-name}Tell the user:
{new-branch-name} based on {parent-branch}{parent-branch} not main{parent-branch} is merged, use /rebase-merged-parent to rebase onto mainAsk if the user wants to create a draft PR now:
Check for a repo-specific PR template at .github/pull-request-template.md or .github/pull_request_template.md. If found, use that format. If not, ask user for confirmation on generating the body ourselves.
#### Create the PR targeting parent branch
~/.claude/skills/stack-branch/scripts/gh-pr-create.sh --draft --base {parent-branch} --title "{type}({scope}): {description}" --body "$(cat <<'EOF'
{body}
EOF
)"If the script is unavailable, fall back to:
gh pr create --draft --base {parent-branch} --title "{type}({scope}): {description}" --body "$(cat <<'EOF'
{body}
EOF
)"~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.