ns-flow-submit

Submits or updates the current Graphite stack by delegating to the ns flow gt submit CLI.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Submitting a Graphite stack involves checkpointing, restack readiness, Graphite publication, and post-submit PR metadata reconciliation. This Skill routes all of that through the ns flow gt submit CLI instead of error-prone hand-written gt submit sequences. ## Core Features & Use Cases - Stack submission: Runs ns flow gt submit from the repository root to checkpoint, restack if needed, and publish the current Graphite stack to GitHub. - PR metadata reconciliation: After publication, re-queries GitHub for exactly the planned branches and generates title/body replacements only for newly created PRs, leaving pre-existing PRs untouched. - Controlled inventory generation: With explicit --generate-pr-inventory authorization (and TTY or --yes confirmation), replaces titles and bodies of every reconciled PR in scope; ns flow generate-pr-inventory targets only the current-branch PR. - Use Case: After stacking three branches with Graphite, ask the agent to submit the stack; the CLI publishes the PRs and fills in generated inventories for the new ones without touching existing PR descriptions. ## Quick Start Ask the agent to submit or update the current Graphite stack so it runs ns flow gt submit from the repository root.

Frequently Asked Questions about ns-flow-submit

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

FAQPage Schema
How do I submit a Graphite stack with this skill?

Ask the agent to submit or update the current Graphite stack, and it runs `ns flow gt submit` from the repository root. The CLI handles checkpointing, restack readiness, Graphite submission, and post-submit PR reconciliation.

Does submitting a Graphite stack overwrite existing PR descriptions?

Ordinary submit edits titles and bodies only for PRs it creates; pre-existing PRs are left untouched. Replacing metadata on all reconciled PRs requires explicit `--generate-pr-inventory` authorization plus a TTY confirmation or `--yes`.

What happens if a restack is required during Graphite submit?

In an interactive session, follow the CLI prompt. In a non-interactive or headless invocation, rerun `ns flow gt submit --restack` only with explicit user approval.

Why did Graphite submit fail after publication?

Submission fails after publication if a planned branch has no open PR, multiple open PRs, malformed lookup data, a query failure, or a changed pre-existing identity. Repair the PR/head-branch association and rerun `ns flow gt submit`.

Can I fall back to running gt submit directly?

Only if the CLI is unavailable and the user explicitly accepts the fallback after seeing the CLI failure. The skill instructs agents not to bypass checkpointing, Graphite submit, or post-submit verification with a hand-written sequence.

Does this skill merge or land pull requests?

No. It only submits or updates the Graphite stack and reconciles PR metadata. Landing or merging PRs is explicitly out of scope.