JSai23
JSai23/claude-tooling
相关职业SOC
基于 SOC 职业分类
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/JSai23/claude-tooling --skill logging-a命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Write high-quality session prompts (SESSION_WORKER.md and SESSION_REVIEWER.md) for an agent loop. Reads repo context and follows the loop-author guide to produce targeted, effective prompts. Use when setting up a new loop or rewriting session prompts for an existing one.
Pre-flight checks and launch for agent loops. Validates branch state, session prompts, creates loop directory structure, and launches run.sh in a tmux session. Use when the user wants to start a new agent loop in the current repo.
Cross-repo visibility for agent loops. Lists running, completed, and crashed loops. Reads the registry and per-repo tracking logs. Shows tmux attach commands. Use when checking what loops are active, what ran recently, or loop details.
正在显示 SKILL.md
基于 SOC 职业分类
| name | logging-a |
| type | action |
| description | Log decisions, progress, deviations, and discoveries during any workflow phase |
| argument-hint | [type: decision|progress|surprise|deviation] |
Action skill — Structured logging: decisions, progress, deviations, discoveries.
$ARGUMENTS
Record a structured log entry in the active plan doc or decision log.
decision)Record a decision with rationale in design-docs/plans/{name}/{name}_decisions.md:
## [YYYY-MM-DD] {Decision Title}
Context: {What prompted this decision}
Decision: {What was decided}
Rationale: {Why — include tradeoffs considered}
Impact: {What this changes about the plan or system}
progress)Add a timestamped entry to the Progress section of the active plan doc:
- [YYYY-MM-DD HH:MM] {What was completed or what state we're in}
surprise)Record an unexpected discovery in the Surprises section of the active plan doc:
### [YYYY-MM-DD] {What was surprising}
Expected: {What we thought would happen}
Actual: {What actually happened}
Implication: {How this affects the plan or approach}
deviation)Record a deviation from the plan. Adds to both the decision log and the plan doc:
## [YYYY-MM-DD] Deviation: {title}
Original plan: {What the plan doc said}
Actual approach: {What we're doing instead}
Reason: {Why the change was necessary}
Impact: {Effect on remaining milestones}
design-docs/plans/ for active plans or locate the active plan in the relevant scope)