メニュー
Use when summarizing a session and updating PROJECT_STATUS.md with important changes, decisions, active experiment state, new constraints, or new files. Triggers: update project status, summarize session, handoff, record changes, keep PROJECT_STATUS current, end of session.
Use when you want to commit and push recent changes to GitHub. Automatically summarizes what changed into a short commit message, then runs git add ., git commit, and git push. Triggers: commit, push, sync to github, save changes, git commit and push.
Use when analyzing RL training status from W&B or local logged metrics, especially actor KL loss, PPO KL, grad norm, clipfrac, critic score/reward/advantages, response length, global sequence length, entropy, invalid draft rates, and diagnosing failures by checking run config and Search-R1/verl implementation.
| name | update-project-status |
| description | Use when summarizing a session and updating PROJECT_STATUS.md with important changes, decisions, active experiment state, new constraints, or new files. Triggers: update project status, summarize session, handoff, record changes, keep PROJECT_STATUS current, end of session. |
| argument-hint | Describe what was done this session, or leave empty to auto-detect from session memory and recent file changes. |
Compact the important outcomes of the current session into PROJECT_STATUS.md. Do NOT write a diary. Replace stale bullets; add only what is new and durable.
Read session memory if it exists:
/memories/session/plan.md or any file under /memories/session/Then read the current PROJECT_STATUS.md in full to understand what is already there.
Categorize each change into one of:
| Category | Goes Into |
|---|---|
| New or moved key file / script | Workspace Map |
| Code path added or behavior changed | Critical Code Paths |
| Algorithm rule, constraint, or "do not" | Algorithm Notes or Do Not Forget |
| Active run metrics / experiment state | Active Run And Monitoring |
| High-level focus shift | Current Focus |
Discard: timestamps, full log excerpts, chat history, API keys, W&B run IDs.
Consult section-rules.md for per-section update rules.
The core rule: replace stale bullets, do not append history.
Use multi_replace_string_in_file for all edits in a single call when possible.
Include ≥ 3 lines of surrounding context in each oldString so replacements are unambiguous.
Do NOT rewrite entire sections. Make surgical replacements.
After writing, re-read the edited sections and confirm:
name field in this SKILL.md still matches the folder name (update-project-status)