toggle-track-logic

星标1

分支0

更新时间2026年7月23日 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.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

来源

gpu-cli

gpu-cli/skills

打开 GitHub 仓库查看创作者相关仓库

下载

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.

同仓库更多 Skills

同仓库

logic

gpu-cli/skills

Use when the user wants to start or stop recording a branch decision trail, record a decision and its rationale, or show and audit the rationale behind a branch or PR. Invoke as /logic toggle, /logic track, or /logic show. Captures decisions across concurrent worktrees, validates evidence, and can add a reviewable trail to a PR.

2026-07-281

lyrebird

gpu-cli/skills

Use when the user wants to establish a brand or personal writing voice, brainstorm content ideas, hone a content thesis, write platform-native posts for Blog, LinkedIn, Reddit, or X, or modify an existing post for another platform. Creates and reads VOICE.md, researches current platform guidance, fact-checks claims, and outputs social posts under social/<proposal-slug>/.

2026-06-151

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

research-spike

gpu-cli/skills

Conducts time-boxed technical investigations, competitive research, or feasibility analysis. Asks clarifying questions upfront and produces a structured markdown report with executive summary. Use for technical spikes, architecture decisions, or evaluating new technologies.

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.