메뉴
Dry-run the progressive-disclosure pass: inspect a knowledge file's staging zone, propose a theme per staged entry, author gists, and show the digest plan — WITHOUT moving anything. Use to preview how LEARNINGS.md / DECISIONS.md would fold into themes when a file grows large.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Dry-run the progressive-disclosure pass: inspect a knowledge file's staging zone, propose a theme per staged entry, author gists, and show the digest plan — WITHOUT moving anything. Use to preview how LEARNINGS.md / DECISIONS.md would fold into themes when a file grows large.
Scaffold a pull-request body from the current branch's commits, Spec: trailers, and closed TASKS into gitignored inbox/ for the human to paste. Use when preparing or opening a PR for a ctx branch. Never pushes and never creates the PR.
Enrich architecture artifacts with code intelligence data. Takes existing /ctx-architecture output as baseline, verifies and quantifies with GitNexus MCP (blast radius, execution flows, domain clustering, registration sites). Run after /ctx-architecture, not instead of it.
Recall project context and present structured readback. Use when the user asks 'do you remember?', at session start, or when context seems lost.
Recall project context and present structured readback. Use when the user asks 'do you remember?', at session start, or when context seems lost.
Consolidate redundant entries in LEARNINGS.md or DECISIONS.md. Use when ctx drift reports high entry counts or entries overlap.
| name | ctx-digest |
| description | Dry-run the progressive-disclosure pass: inspect a knowledge file's staging zone, propose a theme per staged entry, author gists, and show the digest plan — WITHOUT moving anything. Use to preview how LEARNINGS.md / DECISIONS.md would fold into themes when a file grows large. |
Preview how a bounded knowledge root would digest its staging zone into themes — and move nothing. This is the dry-run half of progressive disclosure (see specs/progressive-disclosure.md): it proposes and shows a plan; a later milestone's apply step does the moving.
This skill never edits a knowledge file, never creates a theme file, and never runs an apply/move. Its entire output is a proposed plan for a human to review.
## sections, not ## [ entries;
staged-entry digestion there is a separate milestonectx disclosure inspect .context/LEARNINGS.md --json
This reports, as JSON: the kind, the staging entries (timestamp +
title, un-digested), and the current themes (name, gist, link). Read
it; do not parse the file by hand.
If staging is empty, there is nothing to digest — say so and stop.
For each staged entry, assign it to a theme — an existing theme (by name) or a new one. This is a semantic judgement: group entries that share a subject (e.g. "hook mechanics", "error handling", "OpenCode integration"), not by date.
For each theme in the plan, write the gist — one line, soft ceiling
~140 chars, saying what the theme covers (the shape of its knowledge),
not listing its entries. "hook mechanics: output channels, key names,
compliance wiring" — not "entry A; entry B". The gist tells a future
reader whether to drill in, nothing more. (Spec: ### Gist format.)
Show the human, per theme:
Theme: <name> → .context/<noun>/<slug>.md (would create/append)
gist: <proposed one-line gist>
entries (N):
- [<ts>] <title>
- …
End with an explicit note: "Dry run — nothing was moved or written. The apply step (a later milestone) performs the move." Do not edit any file. Do not run an apply command (there is none yet).
ctx disclosure inspect --json; did not hand-parse the file