reset-gc-branch

Clear an existing gc-branch for a fresh onboarding flow.

32|6|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/handsupmin/gc-tree --skill reset-gc-branch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reset-gc-branch
Source: https://github.com/handsupmin/gc-tree/tree/main/skills/reset-gc-branch
Command: npx skills add https://github.com/handsupmin/gc-tree --skill reset-gc-branch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes stale context from an existing gc-branch so you can start that branch over cleanly when the current state is no longer useful.

Core Features & Use Cases

  • Branch Reset Workflow: Clears the selected gc-branch while preserving the ability to onboard it again afterward.
  • Controlled Restart: Helps when a branch already contains imported context, but the user wants a fresh onboarding pass.
  • Operational Safety: Encourages explicit branch confirmation before taking the reset action to avoid accidental loss of branch context.

Quick Start

Tell me which gc-branch you want to reset, and I will clear its current context so you can onboard it again from scratch.

Frequently Asked Questions about reset-gc-branch

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

FAQPage Schema
How do I reset branch context to start onboarding over from a clean state?

You reset branch context by confirming the target branch name and issuing an explicit reset command, which clears the imported context and enables a fresh onboarding pass for that branch.

What happens to my imported context when I clear a gc-branch?

Clearing a gc-branch removes the existing reusable context from that branch while preserving the ability to onboard it again, allowing a controlled restart of the context workflow.

Why does resetting a branch require explicit confirmation of the branch name?

Explicit branch name confirmation is required before clearing context to ensure operational safety and prevent accidental loss of reusable branch context during the reset.

When should I clear an existing branch context instead of creating a new one?

You clear an existing branch context when the current state is no longer useful but you want to restart onboarding for that specific branch, preserving the branch identity while removing its stale context.

Can I reuse a branch after clearing its context for a fresh onboarding pass?

Yes, the reset workflow specifically preserves the branch so you can onboard it again from a clean state, allowing you to reuse the branch for a fresh context onboarding pass.