step-notes
Turns the status-line gate for step notes on or off. While on, a hook asks for a short status line naming each tool action, like a progress caption, so the user can follow the session. Use when the user types /step-notes or asks to turn step notes on or off.
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 7
- Forks
- 1
01 前言 Front Matter
- name
- step-notes
- description
- Turns the status-line gate for step notes on or off. While on, a hook asks for a short status line naming each tool action, like a progress caption, so the user can follow the session. Use when the user types /step-notes or asks to turn step notes on or off.
- argument-hint
- [on | off | status]
02 资源文件 6
03 SKILL.md 正文
/step-notes
The step-notes gate is a PreToolUse hook (hooks/blocking/step_note_gate.py). It is off by default. While it is on, each message that calls a tool starts with a short status line naming the action, such as "Reading hooks.json." or "Running the gate tests." A call with no status line fails with "Status line missing".
Run the toggle
Pass the user's argument through. With no argument, the toggle flips the current state.
Run python "${CLAUDE_SKILL_DIR}/scripts/toggle_step_notes.py" <on|off|status>.
Tell the user the line the script prints. The change applies at once, to every session on this machine.
Status lines
A status line names the action and its target in a few words. One status line covers every call in the same message. Subagent calls pass without a check.
Layout
| File | Role |
|---|---|
SKILL.md |
This flow: run the toggle, add status lines while the gate is on |
scripts/toggle_step_notes.py |
The on, off, flip, and status CLI for the flag file |
scripts/test_toggle_step_notes.py |
Behavior tests for each action |
scripts/step_notes_constants/config/constants.py |
Flag path, action names, report lines |
04 同仓库更多 Skills
update
Fast-forwards a local repository's main branch to a remote's main after confirming the repo path and source remote through AskUserQuestion. Use when the user says '/update', 'update main', 'fast-forward main', 'sync main from origin', 'pull latest main into <path>', or 'bring main up to date'.
source-command-sr-loop
Converging cleanup loop: repeat /simplify until clean, then repeat /code-review --fix until clean
skill-builder
Skill lifecycle: classify, scaffold, write via the skill-writer-agent, self-audit, compose sub-skills, polish description triggers, enforce deterministic scripts. Triggers: build a skill, new skill workflow, improve this skill, optimize skill description, skill development lifecycle, skill modularity, skill composition, description trigger catalog, deterministic skill scripts.
session-tidy
Audit, clean, and consolidate session logs in the Obsidian vault. Fixes format drift, resolves orphaned next-steps, updates stale statuses, and generates project rollup summaries. Use when session logs feel cluttered or before starting a new project milestone. Triggers on '/session-tidy', 'tidy sessions', 'clean up session logs', 'session audit'.
session-log
Logs a session report as an HTML page, tracks vault context, extracts decisions, and outputs a /rename command. Use for /session-log, 'journal this session', 'log this work', 'session report', 'summarize/log/record this session', 'save session', 'capture session', or 'document what we did'.
run-claude-dev-env
Build, install, run, and test the claude-dev-env installer. Use when asked to run claude-dev-env, install the Claude Code config into ~/.claude, drive the installer, smoke-test it against a sandbox, or run its test suite.