skills.rest
ramontramontini
ramontramontiniCOMMUNITY
Explore all skills by this author →
GitHub

shelve

Shelve an in_progress story by reverting uncommitted changes or preserving commits and adding a Revision Required note.

Updated Apr 7, 2026
Search Tags:#automation#git#workflow#story#shelve#hub-api#revision-required
One-click install
npx skills add https://github.com/ramontramontini/CTEDemo --skill shelve-ramontramontini
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: shelve
Source: https://github.com/ramontramontini/CTEDemo/tree/main/.claude/skills/shelve
Command: npx skills add https://github.com/ramontramontini/CTEDemo --skill shelve-ramontramontini

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Shelve an in_progress story and return it to ready_to_pull with a Revision Required section to ensure continuity across sessions.

Core Features & Use Cases

  • Detects whether code changes are uncommitted or committed-but-incomplete.
  • Reverts uncommitted changes or preserves commits while logging the action.
  • Adds a Revision Required note and transitions the story back to ready_to_pull to resume work later.

Quick Start

Trigger the shelve workflow by providing the STORYID or title to the API; the system will determine the correct path and execute the shelving steps.

Frequently Asked Questions about shelve

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

FAQPage Schema
How do I shelve in-progress git work and return a story to ready_to_pull?▼

To shelve in-progress work, you trigger the workflow with a STORYID or title, which detects uncommitted or incomplete changes, reverts or preserves them, and transitions the story back to ready_to_pull with a Revision Required note.

What happens to uncommitted changes when I shelve a story?▼

When you shelve a story, the system detects uncommitted changes and reverts them locally, logging the action and transitioning the story back to ready_to_pull so work can resume later.

Can I preserve committed but incomplete code changes when shelving a story?▼

Yes, shelving a story detects committed-but-incomplete changes and preserves those commits while logging the action, adding a Revision Required note, and returning the story to ready_to_pull.

What is the best way to release locks and add revision notes when pausing a workflow?▼

The best way to release locks and add revision notes is through the shelve workflow, which coordinates with the Hub API to patch execution logs, release locks, and transition the story back to ready_to_pull.

How does the Hub API coordinate story transitions when shelving work?▼

The Hub API coordinates story transitions by patching execution logs, releasing locks, adding the Revision Required note, and moving the story back to ready_to_pull with robust error handling throughout the process.

Related Skills

Explore More Software Engineering Skills→
ramontramontiniramontramontini

cancel

Cancel stories via API and revert uncommitted code with git checkout.

Community
Advanced
outcomeengoutcomeeng
1

understanding-specs

Load hierarchical product, capability, feature, and story specifications into a structured context summary.

Official
Advanced
martiendejongmartiendejong
1

release-worktree

Release git worktrees after PR creation and log in centralized tracking files.

Community
Advanced
DigicationDigication

task

Save uncommitted work, create branches, and show a workspace dashboard before building.

Official
Advanced