submit

Submit Git-Spice stack changes and update GitHub Change Requests.

1|1|Updated Apr 24, 2026

Search Tags:#release management #pull request #github #git-spice #ci-cd #change request #stack workflow

Ready to run

npx skills add https://github.com/luan/agents --skill submit-luan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: submit
Source: https://github.com/luan/agents/tree/main/pi/agent/extensions/git-tool/skill-resources/git-spice/submit
Command: npx skills add https://github.com/luan/agents --skill submit-luan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It streamlines pushing Git-Spice stack changes and reliably creating or updating GitHub Change Requests, reducing manual PR/CR handling and mismatched descriptions.

Core Features & Use Cases

Stack submission with safer default behavior: Uses update-only by default to update existing Change Requests while skipping stack branches that would create new Change Requests and accidentally publish WIP.
Mode-aware targeting: Supports update-only default submission, single-branch submission, and creating new Change Requests for new stack branches.
Grounded PR/CR description refresh: Fetches the latest GitHub PR title/body for affected PRs and updates descriptions via Skill(pr-descr) so the final output reflects the branch diff without discarding useful PR context.

Quick Start

Run gs stack submit --update-only to push the Git-Spice stack and update the related Change Requests and PR descriptions.

Frequently Asked Questions about submit

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

FAQPage Schema

How do I submit a Git-Spice stack and update GitHub Change Requests?▼

Submit Git-Spice stacks and update GitHub Change Requests by running `gs stack submit --update-only` to push stack updates and sync existing PRs. This automatically aligns PR descriptions with the final branch diffs.

How does stack submission handle work-in-progress branches?▼

Stack submission handles work-in-progress branches by defaulting to update-only mode, updating existing Change Requests while skipping stack branches that would create new PRs, preventing accidental publication of WIP code.

Can I create new Change Requests for new stack branches?▼

Yes, you can create new Change Requests for new stack branches using mode-aware targeting. This switches from the default update-only mode to explicitly create new PRs for new stack branches.

How are PR descriptions refreshed when pushing stack updates?▼

PR descriptions are refreshed by fetching the latest GitHub PR title and body metadata using `gh pr view`, then invoking Skill(pr-descr) to align descriptions with the final branch diffs without discarding useful PR context.

What is the best way to automate Git-Spice stack workflow changes?▼

The best way to automate Git-Spice stack workflow changes is using mode-aware stack submission, which checks stack state, runs the appropriate `gs stack submit` command, and updates PR descriptions to reflect the final branch diffs.