Skip to content
cccskills
FreePublished on GitHub

trailhead-manage

trailhead manage cluster: the admin verbs that keep a trailhead install healthy. Show the effective config or change it through a guided menu (config); check for a newer trailhead and install it where that is safe (update), prune a map's sub-issue edges to reclaim slots under GitHub's 100-cap (prune), and audit closed tickets for regressions against the code and the open ones for duplicates (audit). A cohesion cluster of the trailhead skill split, loading the shared `_shared/` core; reached through the `/trailhead:<verb>` command wrappers and the bare `/trailhead` dispatcher. Not auto-invoked: it runs only when one of these verbs is dispatched.

The English summary is being prepared. Showing the original description.

ToRvaLDz/trailhead29 stars(GitHub 29 + cccskills 0)
Works withGitHub

Run score Not tested

See how to install

Files included (4)

  • SKILL.md4.3 KB
  • references/auditing.md27.2 KB
  • references/pruning.md5.7 KB
  • references/updating.md5.4 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

trailhead-manage is the manage cluster of the trailhead skill: the admin verbs that keep a trailhead install healthy. config shows the effective config or changes it (a guided menu, or get / set <key> <value>); update checks for a newer trailhead and installs it where that is safe; prune reclaims a map's native sub-issue slots under GitHub's 100-cap; audit checks closed tickets for regressions against today's code and finds duplicate or groupable open ones. Everything lives on the GitHub Issues; the repo holds code only.

Load first, in order

Before doing anything, load <skill base>/../_shared/load-first.md and follow it: the shared-core load contract (the six core files, in order, then the effective config). <skill base> is this skill's base directory (Claude Code prints it as Base directory for this skill: when the skill loads; on another host, the directory holding this SKILL.md): resolve the path to an absolute path and open it with the Read tool on that absolute path. Never cd into a skills directory and never read a relative path from the shell (a cd compound followed by a read is denied by the search guard). The same rule covers every later ../_shared/... or references/... path in this skill: resolve it against the base directory to an absolute path before reading. _shared/ is a sibling of this cluster's own directory (at ../_shared/), never a child of it; its absence from a listing of the cluster dir is expected, not a missing core.

These admin verbs resolve no ticket and set up no isolation workspace.

Routing: verb to engine

The first word of the arguments is the verb (config, update, prune, or audit); the rest is that verb's argument (get, set <key> <value>, a map, --all, or empty).

  • config [get|set …] to ../_shared/configuration-reference.md: the config keys, their semantics, and the guided menu setup. With no argument it runs the guided setup; config get prints the merged config read-only (project .trailhead/config.json over global over defaults, showing which source wins each key); config set <key> <value> writes one key directly (to the project .trailhead/config.json, or to ~/.claude/trailhead/config.json with --global). Read that file and follow it.
  • update to references/updating.md: the update protocol (detect the install channel, compare the installed version with the latest from the matching source, install the newer one where it is safe). Read that file and follow it.
  • prune [map] to references/pruning.md: reclaim native sub-issue slots on a map near or at GitHub's 100 sub-issue cap by dropping the edges of closed and orphan tickets and re-adding missing ones, keeping every reference (Parent line, Decisions-so-far pointer, map label). With no argument it prunes the active map. Read that file and follow it.
  • audit [map] [--all] to references/auditing.md: audit the closed tickets since the last audit (or all of them with --all) for regressions against the current code (a fast no-agent path for unchanged code), classing each as implemented, unchanged, evolved, implemented wrong, or not implemented, and compare the open tickets for duplicates and groupable clusters; every fix is a proposal applied only on an explicit yes. With no argument it covers every open map plus the whiteboard; with a map it covers that map only. Read that file and follow it.

The full config key reference is a single source, shared with the rest of the skill: ../_shared/configuration-reference.md (keys + guided setup).

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Start and drive a large project (more than one agent session can hold) as a map of decision tickets on GitHub Issues, resolving one at a time until the way to the destination is clear. Self-contained (zero external-plugin dependencies: trailhead ships its own `trailhead-*` engine agents and needs only an authenticated gh CLI): map-based onboarding and a discuss→plan→execute→verify engine with atomic commits, with everything (map, discussion, plan, verification) living on the Issues. Invoke only when the user explicitly runs `/trailhead` (or a `/trailhead:<verb>` command) or asks to chart, adopt, or work a trailhead map, and do not auto-invoke for generic planning, project, or task-tracking requests.

The English summary is being prepared. Showing the original description.

ToRvaLDz/trailhead29Updated Oct 27, 2026

trailhead capture cluster: the zero-friction captures that record work without breaking flow. Capture a bug ticket (bug), a small build ticket you will do now (todo), a fog idea (idea), a trigger-gated seed (seed), a verbatim note (note). A cohesion cluster of the trailhead skill split, loading the shared `_shared/` core; reached through the `/trailhead:<verb>` command wrappers and the bare `/trailhead` dispatcher. Not auto-invoked: it runs only when one of these verbs is dispatched.

The English summary is being prepared. Showing the original description.

ToRvaLDz/trailhead29Updated Oct 27, 2026

trailhead chart cluster: the verbs that give a map its start or bring outside work into it. Chart a new map from a loose idea (new), adopt an existing codebase into a map (adopt), open a ticket of any type on the fly (ticket), triage issues opened by others into the map (inbox), and run a standalone grilling session (grill). A cohesion cluster of the trailhead skill split, loading the shared `_shared/` core; reached through the `/trailhead:<verb>` command wrappers and the bare `/trailhead` dispatcher. Not auto-invoked: it runs only when one of these verbs is dispatched.

The English summary is being prepared. Showing the original description.

ToRvaLDz/trailhead29Updated Oct 27, 2026

trailhead view cluster: the read-only renders of the trailhead surface. Show the low-res map: destination, decisions, frontier, fog (map); regenerate and show the pinned per-repo dashboard indexing every open map plus the whiteboard (dashboard); show the whiteboard of loose map-less tickets (whiteboard). A cohesion cluster of the trailhead skill split, loading the shared `_shared/` core; reached through the `/trailhead:<verb>` command wrappers. Not auto-invoked: it runs only when one of these verbs is dispatched.

The English summary is being prepared. Showing the original description.

ToRvaLDz/trailhead29Updated Oct 27, 2026

trailhead work cluster: the verbs that resolve tickets on the map and manage a ticket's lifecycle. Work the next frontier ticket or the one you name (work), work one ticket whole without splitting, a new whiteboard ticket or an existing one (quick), checkpoint the ticket in play (pause), resume it from its checkpoint (resume), split an oversized ticket into children (split), and run a chosen scope (one map, the whiteboard, or everything) autonomously until a stop condition or exhaustion (auto). A cohesion cluster of the trailhead skill split, loading the shared `_shared/` core; reached through the `/trailhead:<verb>` command wrappers. Not auto-invoked: it runs only when one of these verbs is dispatched.

The English summary is being prepared. Showing the original description.

ToRvaLDz/trailhead29Updated Oct 27, 2026

See all skills by ToRvaLDz

Report a problem with this skill