ns-flow-gs-autoslot

Moves dirty Git work onto a gh-stack child branch, checkpoints it, and checks it into a managed Slot.

2|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/nseng-ai/ns --skill ns-flow-gs-autoslot-nseng-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ns-flow-gs-autoslot
Source: https://github.com/nseng-ai/ns/tree/main/skills/incubating/flow/ns-flow-gs-autoslot
Command: npx skills add https://github.com/nseng-ai/ns --skill ns-flow-gs-autoslot-nseng-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Uncommitted changes on a trunk or stacked branch are risky and hard to organize. This Skill safely moves dirty work onto a new gh-stack child branch, creates a durable checkpoint commit, and moves that child into a managed ns Slot worktree — with strict preflight checks and forward-only failure handling so nothing is lost. ## Core Features & Use Cases - Two guarded paths: bootstrap a dirty trunk into the first gh-stack branch, or extend an already-tracked stack top with a native gh stack add child. - Verified checkpointing: commits dirty work via ns flow cp only after branch/provider state is proven, then re-verifies a clean worktree before any Slot checkout. - Structured outcome reporting: every invocation ends with an eight-field report covering outcome, mutations, preserved state, recovery guidance, and lesson disposition. - Use Case: You have uncommitted changes on your main branch and want them isolated on a stacked branch inside a managed worktree. Invoke /ns:flow:gs:autoslot and the Skill validates gh-stack 0.1.0, creates the child, checkpoints the work, and checks out a Slot — refusing safely if any precondition fails. ## Quick Start Invoke the /ns:flow:gs:autoslot command with an optional child branch name while your working tree has uncommitted changes on trunk or a tracked stack top.

Frequently Asked Questions about ns-flow-gs-autoslot

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I move uncommitted changes onto a stacked branch with gh-stack?

Invoke the autoslot workflow with a dirty working tree on trunk or a tracked stack top. It creates a child branch via git switch -c or gh stack add, checkpoints the work with ns flow cp, and verifies a clean worktree before any further step.

What is the difference between gh stack init and gh stack add?

gh stack init initializes a trunk child as the first branch of a new stack, used when starting from a dirty trunk. gh stack add extends an existing stack by adding a child above the current tracked top branch.

Which gh-stack version does this workflow require?

The workflow requires gh stack --version to report exactly version 0.1.0. It refuses before any mutation on command failure, missing version output, version drift, or help output, since gh stack version is not valid in this surface.

What happens if the Slot checkout fails after checkpointing?

The failure is reported as a partial failure and the committed provider child is preserved untouched. Recovery starts from inspecting or retrying only the Slot operation; branch creation, provider operations, and checkpointing are never rerun.

Can this workflow extract the latest commit or roll back a branch?

No. It never extracts the latest commit, deletes branches, runs gh stack unstack, or attempts rollback. It follows a forward-only preservation policy because gh-stack offers no safe remove-one-layer rollback and owns private metadata.

Why does the workflow refuse to run on a clean working tree?

A clean invocation is refused because the skill only handles dirty-state transfer. Slot composition does not relax autobranch eligibility, and a clean tree would imply a latest-commit move, which this skill explicitly does not support.