log-progress
Append one entry to REVIEW_HISTORY.md. Use after a panel, task, verifier, or risk decision, or when the user says /log_progress. Append-only from this skill; review_orchestrator may drop entries older than 30 days after other harness tasks via scripts/trim_review_history.py.
- License 许可
- MIT
- 所属仓库
- sazlin/loadout
- 最近更新
- 2026-11-14
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- log-progress
- description
- Append one entry to REVIEW_HISTORY.md. Use after a panel, task, verifier, or risk decision, or when the user says /log_progress. Append-only from this skill; review_orchestrator may drop entries older than 30 days after other harness tasks via scripts/trim_review_history.py.
02 资源文件 4
- 参考文档evals/evals.json508 B
- 参考文档evals/files/REVIEW_HISTORY.md178 B
- 参考文档references/review-history-template.md574 B
- 脚本scripts/trim_review_history.py2.8 KB
03 SKILL.md 正文
Log progress
Append-only history for the PR-review harness.
When to use
- After panel dispatch/results, each resolved task, each verifier claim batch, the risk decision, and when the harness aborts because the PR merged
- The user asks
/log_progress
Steps
- If
REVIEW_HISTORY.mddoes not exist at the project root, create it fromreferences/review-history-template.md. - Append one entry. Never rewrite, truncate, or reorder prior entries from this skill.
- Fill: timestamp (ISO), agent, phase (
panel|resolve|verify|decision|abort), optional task id, one-paragraph summary, outcome (ok|blocked|false_claim|merged|wait_for_human|aborted). Put deferred minors on the Deferred minors: template field (noneorid (title)display lines fromdeferred_minors[]). Do not also list those ids in the summary paragraph.
Do not commit this file as part of a product fix. Do not edit
VERIFIERS.md or source.
Guardrails
- Never delete or rewrite history from this skill
- Never log secrets or raw PII; redact
Retention (orchestrator only)
review_orchestrator drops entries older than 30 days after all other
harness tasks complete, using scripts/trim_review_history.py. Do not trim
from this skill. Append only during the run.
04 同仓库更多 Skills
demo
Demo skill
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
using-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback