메뉴
Fill in the Patterns & Surprises section of the latest session reflect file and write the completed review to .ctx/logs/self-review/. Use when the user runs "/self-review", asks to "fill in the reflect", "write the session review", or "what patterns did we hit".
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when the user runs "/insights-audit", asks to "validate the insights report", "audit the report against my projects", "check what the report got wrong", or wants to cross-check an /insights-generated HTML report against actual GitHub repos and local project directories.
This skill should be used when the user asks to "end session", "capture state", "session summary", "what changed this session", "summarize repos", "write session notes", or wants to capture multi-repo state at the end of a work session.
Use when working on the rslm project — Recursive Language Model inference engine in Rust. Triggers on "rslm", "RLM", "recursive language model", "rhai built-ins", "ctx_grep", "ctx_slice", "rlm_call", "rslm-core", "rslm-providers", "rslm-store", or any question about running queries, ingesting documents, or writing Rhai scripts for the RLM loop.
This skill should be used when the user asks to "review this diff", "ai review", "security review my changes", "review before push", "check my code for issues", or wants an LLM-based security and correctness review of uncommitted or unpushed changes.
This skill should be used when the user asks to "generate commit message", "write a commit msg", "ai commit", "generate a conventional commit", "write my commit", or wants an LLM to draft a commit message from the staged diff.
Use this skill when the user says "build a harbor adapter", "adapt this benchmark for harbor", "harbor adapter for X", "port this benchmark to harbor", or wants to integrate any benchmark dataset into the Harbor evaluation framework (https://harborframework.com).
| name | self-review |
| description | Fill in the Patterns & Surprises section of the latest session reflect file and write the completed review to .ctx/logs/self-review/. Use when the user runs "/self-review", asks to "fill in the reflect", "write the session review", or "what patterns did we hit". |
| argument-hint | [optional: repo path — defaults to cwd] |
| allowed-tools | Read, Write, Edit, Bash, Glob |
Analyse the latest session reflect file, fill in the Patterns & Surprises section, and
write the result to .ctx/logs/self-review/.
ls -t .ctx/reflect-*.md 2>/dev/null | head -1
If none found, report and stop.
Read the full file. Extract:
## Shipped## Files changed## Patterns & SurprisesFor each of the four placeholder subsections, reason from the commit list and diff stat:
Look for: repeated fix/retrigger commits on the same thing (e.g. multiple ci: retrigger
commits indicate a stuck workflow), large diff counts on unexpected files, or commits whose
subject suggests rework (fix(ci), fix: update ... regression).
Look for: single-commit features that landed cleanly, quality gates that passed first try (no follow-up fix commits), refactors with no test regressions.
Look for: commits that address something not in the original intent (e.g. fix: close clone closure and pipe fds appearing after CI work suggests a latent bug surfaced during review),
doc-only fixes following code changes, unexpected breakages caught by hooks.
Reason forward: given what took long, what setup or guard would prevent it next time? Examples: a CI lint job that catches drift earlier, a pre-push check that validates a previously manual step, a rate-limit on version bumps that prevents noisy commits.
Keep each section to 2-4 bullet points. Be specific — reference commit SHAs or file names where relevant. Do not use generic filler.
Replace the four (fill in next session) placeholders in the reflect file with the
filled-in content (edit in-place).
Write a copy to .ctx/logs/self-review/ using the same filename:
mkdir -p .ctx/logs/self-review
cp .ctx/reflect-<date>.md .ctx/logs/self-review/reflect-<date>.md
Print a one-line confirmation:
self-review: wrote .ctx/logs/self-review/reflect-<date>.md
Then print the filled-in ## Patterns & Surprises section so the user can read it inline.
- Nothing notable this session.## Open questions section is separate — leave it as-is unless the user asks to fill it.