toggle-track-logic

Stars1

Forks0

UpdatedJuly 23, 2026 at 20:14

Use to turn the decision trail on or off for a branch. Invoke as /toggle-track-logic [on|off] [branch] — no state flips the current setting, no branch targets the current checkout. Enabling materializes the committed .logic/ runtime and the capture hooks. Use when the user asks to start or stop tracking decisions/rationale/logic for a branch or the repo.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Source

gpu-cli

gpu-cli/skills

View GitHub Repository View Creator Repositories

Download

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	toggle-track-logic
description	Use to turn the decision trail on or off for a branch. Invoke as /toggle-track-logic [on\|off] [branch] — no state flips the current setting, no branch targets the current checkout. Enabling materializes the committed .logic/ runtime and the capture hooks. Use when the user asks to start or stop tracking decisions/rationale/logic for a branch or the repo.
argument-hint	[on\|off] [branch]
user-invocable	true
license	Apache-2.0

toggle-track-logic

Turns decision-trail tracking on or off, per branch, and installs the runtime on first enable.

Command

bash .agents/skills/logic-core/scripts/toggle.sh [on|off] [branch]

No on|off → flip the current effective state for the branch.
No branch → the current checkout's branch.
Naming a branch other than the current checkout writes the config change here, where it cannot govern that branch yet. The command says so and tells the user what to do: run it from that branch's worktree if one exists, or commit the config change onto that branch. Relay that instruction; do not report the toggle as already in effect there.
Enabling runs install-hooks.sh: it materializes .logic/ (config, engine, git post-commit hook, Claude Code hook scripts), sets core.hooksPath, and prints the settings snippet for the optional enrichment gate.

Always report back the resulting state, the branch it applies to, and the storage backend — the command prints exactly this. A silent flip on the wrong branch is how trails quietly fail to happen, so never suppress that line.

After enabling

Tell the user to commit .logic/ so hooks and config travel with the branch and into any worktrees:

git add .logic && git commit -m "chore: enable decision-trail tracking"

If they want the Layer-2 enrichment gate (agents get prompted to explain commit stubs before finishing), have them merge the printed hooks block into .claude/settings.json. It is optional; the git hook captures rows regardless.

Config and precedence

Tracking is governed by .logic/config.json (see the config-schema reference in logic-core). For the current branch, precedence is: an exact branch key, a glob key (release/*), then an enabled branch that is an ancestor of HEAD (so a derived worktree branch forked from an enabled feature branch is tracked and its rows are labeled with that feature branch), then the project default.

You can also edit config directly:

bash .agents/skills/logic-core/scripts/config-edit.sh set default on
bash .agents/skills/logic-core/scripts/config-edit.sh set-branch release/* off
bash .agents/skills/logic-core/scripts/config-edit.sh set-storage some-branch tsv

Toggle dirt is intended

config.json is committed, so enabling or disabling a branch shows up in that branch's PR diff. That is a feature, not noise: the diff records that tracking was on for the work under review.

More from this repository

same repository

logic-core

gpu-cli/skills

Shared engine for the decision-trail suite (track-logic, toggle-track-logic, show-logic). Not invoked directly — it provides the storage, config, branch resolution, capture hooks, and read/audit/reconstruct helpers the three commands call. Read this to understand or maintain the runtime.

2026-07-241

show-logic

gpu-cli/skills

Use to show the decision trail for the current branch — what was decided, why, with what perceived confidence, and on what evidence — as a reviewable table plus decision-quality notes. Invoke as /show-logic [branch] [--pr]. Collects rows across parallel worktrees, validates evidence against the diff, flags conflicts and problematic choices, and reconstructs a best-effort trail (clearly marked) when tracking was off. Use when the user asks to see or audit the rationale/logic/decisions behind a branch or PR, or to add it to a PR.

2026-07-241

track-logic

gpu-cli/skills

Use to record a decision in the branch's decision trail — why a fork was chosen, an approach rejected, a scope call made, and the decision-maker's perceived confidence — by you or on the user's behalf. Owns the row protocol the whole logic suite shares. Invoke as /track-logic "<what> because <why>" [--confidence high|medium|low], and follow its capture rules whenever tracking is on for the branch.

2026-07-241

skill-shield

gpu-cli/skills

Security audit and active remediation for agent skills. Analyzes SKILL.md instructions and bundled scripts for prompt injection, data exfiltration, excessive permissions, supply chain risks, and other threats. Presents findings inline, optionally generates reports, and can rewrite skills to remove security concerns.

2026-02-241

tui-clone

gpu-cli/skills

Explore and analyze TUI applications to document their features for cloning. Use when asked to reverse-engineer, analyze, document, or understand a terminal UI like Claude Code, OpenCode, Codex, lazygit, or any ratatui/ncurses-based application. Launches the target TUI in tmux, systematically explores all views and keybindings, captures ASCII diagrams of each screen, and writes findings incrementally to a markdown file (survives context compaction).

2026-02-181

context-curation

gpu-cli/skills

Analyzes staged git changes and evaluates agentic context files (Claude, Codex, Cursor, etc.) to suggest additions or removals. Use after staging changes before committing.

2026-01-291

name	toggle-track-logic
description	Use to turn the decision trail on or off for a branch. Invoke as /toggle-track-logic [on\|off] [branch] — no state flips the current setting, no branch targets the current checkout. Enabling materializes the committed .logic/ runtime and the capture hooks. Use when the user asks to start or stop tracking decisions/rationale/logic for a branch or the repo.
argument-hint	[on\|off] [branch]
user-invocable	true
license	Apache-2.0

toggle-track-logic

Turns decision-trail tracking on or off, per branch, and installs the runtime on first enable.

Command

bash .agents/skills/logic-core/scripts/toggle.sh [on|off] [branch]

No on|off → flip the current effective state for the branch.
No branch → the current checkout's branch.
Naming a branch other than the current checkout writes the config change here, where it cannot govern that branch yet. The command says so and tells the user what to do: run it from that branch's worktree if one exists, or commit the config change onto that branch. Relay that instruction; do not report the toggle as already in effect there.
Enabling runs install-hooks.sh: it materializes .logic/ (config, engine, git post-commit hook, Claude Code hook scripts), sets core.hooksPath, and prints the settings snippet for the optional enrichment gate.

After enabling

Tell the user to commit .logic/ so hooks and config travel with the branch and into any worktrees:

git add .logic && git commit -m "chore: enable decision-trail tracking"

Config and precedence

You can also edit config directly:

bash .agents/skills/logic-core/scripts/config-edit.sh set default on
bash .agents/skills/logic-core/scripts/config-edit.sh set-branch release/* off
bash .agents/skills/logic-core/scripts/config-edit.sh set-storage some-branch tsv

Toggle dirt is intended

config.json is committed, so enabling or disabling a branch shows up in that branch's PR diff. That is a feature, not noise: the diff records that tracking was on for the work under review.