Repackages a Graphite stack into Decision PRs and Span PRs with local-only slicing and squashing.
npx skills add https://github.com/nseng-ai/ns --skill code-smush-nseng-ai
Please help me install this Agent Skill. Skill: code-smush Source: https://github.com/nseng-ai/ns/tree/main/skills/internal/code/code-smush Command: npx skills add https://github.com/nseng-ai/ns --skill code-smush-nseng-ai
-st2) for previously packaged or PR-associated stacks. - Safety contract: Local-only operation with no git push, gh, or gt submit; requires explicit ratification of the proposed Slice Map, timestamped backup branches before any mutation, and per-boundary validation in temporary worktrees. - Use Case: You have a 20-commit feature branch mixing three major design choices with implementation fallout. Invoke smush to get a ratified Slice Map, then a validated stack of grammar-named branches like retry-budgets--02d-per-call-budgets ready for you to submit yourself. ## Quick Start Ask the agent to smush the current Graphite stack into Decision and Span PRs, selecting an owning Objective when prompted.High-intent search queries and answers about installing and using this skill.
Invoke smush explicitly on the stack; it classifies commits into Decision PRs and Span PRs from narrated commit messages, proposes a Slice Map, and after your ratification creates grammar-named slice branches locally. Submission to GitHub remains your responsibility afterward.
A Decision PR encodes one high-impact choice plus the minimal commits needed to judge it in isolation. A Span PR holds a maximal stretch of consequence-executing commits between decisions and gets squashed into one commit with a narration digest.
No. Smush is strictly local-only: it never runs git push, gh, or gt submit, and never creates, updates, or closes pull requests. It reports the old stack as close candidates, but every PR decision belongs to the user.
Yes, via replacement construction. Smush builds a new stack alongside the old one with a generation token like -st2 in branch names, leaving the original branches, Graphite metadata, and PR associations untouched.
Smush first moves the cut to a nearby commit that validates, then tries fixing forward into the slice with gt modify, and finally escalates to you. Every slice boundary must pass the repository validation entrypoint in a temporary worktree.
Cuts land only on commit boundaries, so a too-coarse commit cannot be split. Squashed span interiors are unrecoverable except through the narration digest, and submitted replacement stacks re-run CI across the full new stack.
wahidyankfStress-test project plans and technical designs with structured multiple-choice questioning.
nthpaulRestack and submit Graphite pull request stacks after local commits.
remix-runClose an old GitHub pull request and validate the replacement PR state.
Knuckles-TeamAutomate Git history fixes using rebase, cherry-pick, and bisect workflows.