Preserves a long-lived repository's engineering context — an architecture index, an impact map, session records, and the decisions behind them — as markdown committed beside the code, so an agent reads instead of rediscovering. Repository-local, no network, Python stdlib, MIT.
Skill Claude CodeCodex
Set up chamnan in this repository for the first time — build the architecture index, measure how well the code describes itself, fill in missing file comments, and record a baseline. Run once per repo.
Skill Claude CodeCodex
Write down a procedure worth keeping — a multi-step process, a trap that cost real time, or something that has now come up three times. Use it the moment you finish such a task, while the details are still exact.
Skill Claude CodeCodex
Record a change that reshaped the repository — what moved, why it was worth doing, and which areas it touched. Use after a migration, a rewrite, or a decision that changed how part of the system works.
Skill Claude CodeCodex
Turn a scratch script into a permanent tool this repo keeps. Use when a check, report, or analysis has proved worth running more than once.
Skill Claude CodeCodex
Rebuild the architecture index after files were added, removed, renamed, or restructured. Cheap to run; run it whenever the shape of the repo changed rather than waiting to be asked.
Skill Claude CodeCodex
Record why something is the way it is — a decision and its reasoning, a lesson that cost time, or a standing constraint. Use when the reasoning behind a choice would be expensive to reconstruct later.
Skill Claude CodeCodex
Show what this workspace has actually done to context cost in this repo — weekly context-per-turn, before and after. Use when the user asks whether chamnan is worth keeping.
Skill Claude CodeCodex
Write down where this stretch of work stopped, so the next session continues instead of restarting. Use at the end of a working session, or when handing the repository to someone else.