菜单
Use when asked to summarize recent repo activity, show what happened, or give a timeline view of work — with or without a time window argument
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | devloop-standup |
| description | Use when asked to summarize recent repo activity, show what happened, or give a timeline view of work — with or without a time window argument |
Runs devloop council analysis + git log to produce a narrative timeline of recent repo activity.
/devloop-standup or /devloop-standup 48h)The skill accepts an optional time argument: 1h, 6h, 24h, 48h, 7d, etc.
Parse from the invocation args. If absent, use 24h. Convert to git --since value:
24h → --since="24 hours ago"7d → --since="7 days ago"2h → --since="2 hours ago"git log --format="%ad %s" --date=format:"%H:%M" --since="24 hours ago"
Group by rough time-of-day block: Early morning (00–06), Morning (06–12), Afternoon (12–17), Evening (17–21), Late evening (21–24).
If the standup covers structural changes (new crates, major refactors), freshen the knowledge graph first:
gkg index /path/to/repo
export OPENAI_API_KEY=$(grep ^OPENAI_API_KEY ~/.secrets | cut -d= -f2)
~/.local/bin/devloop analyze --council --council-mode extensive --repo /path/to/repo
Use the council's summary, patterns, and recommendations as the analytical backbone. If the council flags specific work as a "saga" or investigation, name it.
Write in this style — narrative, not structured report:
Single branch (main), N commits, X sessions.
All work on YYYY-MM-DD:
- **Morning (HH:MM–HH:MM):** [what happened, what was built/fixed, what was the arc]
- **Afternoon (HH:MM–HH:MM):** [...]
- **Evening (HH:MM–HH:MM):** [...]
- **Late evening (HH:MM–HH:MM):** [name the saga if there was one — e.g. "cgroup debugging saga"]
[1-sentence close: what the session ended with / the outcome]
Rules:
To record the standup in the Obsidian vault, use devloop-daily-update skill after synthesis.
source ~/.secrets doesn't export — use the explicit export form above.
Single branch (main), 52 commits, 3 sessions.
All work on 2026-03-16:
- Early morning (00:54–07:48): Hexagonal architecture refactor in 5 phases — domain traits, adapters, DI in handlers, mock tests, conformance suite. Cross-platform adapters for Windows/macOS/GKE added.
- Afternoon (13:46–16:57): GKE unprivileged adapter suite, Zombienet pattern analysis, RuntimeCapabilities trait, state persistence across daemon restarts.
- Evening (16:35–18:57): Ops runtime — VPS setup, systemd unit, install script, Justfile. Cgroup debugging began: controllers not delegating.
- Late evening (21:31–23:01): Cgroup delegation saga — chased DelegateSubgroup=yes/supervisor confusion, diagnosed no-internal-processes constraint, fixed with supervisor leaf cgroup pattern. Confirmed
minibox run alpine -- /bin/trueworking.Session closed clean: all commits pushed, cgroup fix verified on VPS.
Deep codebase analysis — architecture health, test coverage gaps, tech debt, and actionable findings
Run pre-commit checks (fmt, clippy, test) then stage, commit, and push with a conventional message
Review staged or recent changes for correctness, style, and Rust conventions before committing
Use when SSHing into remote machines, looking up credentials, renaming Tailscale devices, or accessing services on the tailnet. Symptoms - SSH auth failures, too many authentication failures, command not found tailscale, need to find credentials for remote machines.
Use when mixing Tokio async code with synchronous blocking I/O libraries (tar, flate2, zip, csv), or when seeing "cannot block the current thread from within the async context" panics, or needing to stream async bytes into a sync reader.
Structured BAML schema edit → validate → test loop for the devloop project. Use when editing any *.baml file in crates/baml/baml_src/ — covers version parity gotchas, uvx invocation, regeneration workflow, and the analyze verify step.