code-workflows

Routes requests to rare code workflow playbooks for Graphite stacks, CI debugging, and parity review.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Rare but complex code workflows—deleting Graphite stacks, splitting branches into stacked PRs, coordinating multi-slice implementations, debugging GitHub Actions failures, and reviewing cross-harness parity—require detailed playbooks that would bloat context if always loaded. This Skill acts as a lazy-loading router that keeps the installed surface small and loads the full playbook only after a route is selected. ## Core Features & Use Cases - Route-based playbook loading: Maps routes and aliases (delete-stack, stackify-branch, stacker-agent, parity-review, gh-ci-debug) to reference playbooks loaded on demand. - Safe destructive operations: The delete-stack playbook enforces explicit authorization, dirty-worktree refusal, and slot cleanup before deleting Graphite branches, PRs, and remotes. - Serial multi-slice coordination: The stacker-agent playbook normalizes freeform plans into slice manifests, runs one worker per slice, and verifies structured handoffs before advancing. - Use Case: A developer pastes a failing GitHub Actions run URL; the gh-ci-debug route resolves the run, streams only failed logs, identifies the root cause in the workflow YAML, and proposes a minimal fix with a rerun command. ## Quick Start Ask the agent to load a code workflow by name, for example to debug a failing CI run or split the current branch into a Graphite stack.

Frequently Asked Questions about code-workflows

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

FAQPage Schema
How do I delete a Graphite stack safely?

Use the delete-stack route with an explicit root branch. It discovers the target subtree, refuses dirty worktrees, frees occupied slots, closes authorized PRs with gh pr close --delete-branch, then runs gt delete --upstack and verifies no local or remote refs remain.

How to split one branch into stacked PRs with Graphite?

The stackify-branch route compares the branch to trunk, plans semantic slices ordered by dependency, preserves the original branch as a fallback, rebuilds each slice with gt create, validates with repo checks, and optionally submits with gt submit.

How do I debug a failing GitHub Actions run from a URL?

The gh-ci-debug route extracts the run ID and repo from the URL, runs gh run view for annotations, streams only failed logs with --log-failed, maps errors to workflow YAML steps, and reports a diagnosis with a minimal fix and rerun command.

Can stacker-agent run slices in parallel?

No. The stacker-agent protocol is strictly serial: one worker per slice, and the coordinator must verify the structured handoff, head SHA, and diff before starting the next slice. Parallel execution is explicitly listed as an anti-pattern.

When should I not use the stacker-agent workflow?

Avoid it when the working tree is dirty, the plan normalizes to fewer than two slices, the repo workflow tool is missing, or the harness only supports isolated worker workspaces. Single-slice work should be implemented directly in-session instead.