update-global-context

Updates durable global-cache context for the active gc-branch using guided JSON after confirming branch and document resolution.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you capture durable changes from recent work and convert them into shared global context for the active gc-branch, so you do not keep re-explaining the same facts.

Core Features & Use Cases

  • Durable context updates: Convert newly learned conventions, terms, and repo-specific knowledge into reusable documentation.
  • Branch-aware workflow: Confirm the active gc-branch before making changes and avoid re-onboarding a branch that already contains context.
  • Targeted doc updates: Resolve the right document, preserve useful existing details, and apply structured updates without inventing new fields.

Quick Start

Use this skill to update the active gc-branch with a durable new fact or convention after confirming the branch and resolving the target document.

Frequently Asked Questions about update-global-context

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

FAQPage Schema
How do I update durable global context for an active gc-branch?

To update durable global context for an active gc-branch, confirm the branch, resolve the target document, apply the structured update JSON, and verify the changes before reporting success.

What is durable global context for multi-repo workflows?

Durable global context for multi-repo workflows is shared repository knowledge that captures learned conventions and facts, preventing you from re-explaining the same information across different sessions.

How do I convert learned conventions into shared repository knowledge?

You convert learned conventions into shared repository knowledge by applying guided update JSONs to resolved documents within an active gc-branch, preserving existing details without inventing new fields.

Do I need to confirm the active gc-branch before applying context updates?

Yes, branch confirmation is required before applying context updates to ensure changes target the correct active gc-branch and avoid re-onboarding a branch that already contains the context.

What's the best way to manage onboarding knowledge across multiple sessions?

The best way to manage onboarding knowledge across multiple sessions is updating durable global context on a gc-branch, which captures newly learned terms and repo-specific facts for reuse.

Why does global context update require immediate verification before reporting success?

Global context updates require immediate verification before reporting success to ensure the guided update JSON applied correctly to the target document and the shared repository knowledge is accurately captured.