Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
Git and cursor-mirror are two introspection systems that mesh via commit IDs:
Git: "What changed?" → abc123
Cursor-Mirror: "Why?" → events 140-148
Thoughtful Commitment: Links them together
Protocol: THOUGHTFUL-COMMITMENT
Commit Message Format
<type>: <summary> (imperative, <50 chars)
<narrative>
What happened, from whose perspective, and why it matters.
Focus on intent and motivation, not just mechanics.
<changes>
- Bullet list of mechanical changes
- For quick scanning
<thinking-ref>
Thinking: cursor-mirror://<composer>/<event-range>
Types
Type
Use
feat
New feature or capability
fix
Bug fix
refactor
Code restructuring (no behavior change)
docs
Documentation only
style
Formatting (no code change)
test
Adding or updating tests
chore
Maintenance tasks
narrative
Story beat, character change, world evolution
For MOOLLM narratives, the type can be the story beat:
Incarnation Ceremony: Kittens receive emoji souls
Midnight Prowl: Cats explore the moonlit garden
Cat Council: Biscuit accepted into family
Context Gathering
Before writing commits or PRs, gather existing messages to match style and avoid repetition:
See examples/git-commands.yml → context_gathering for complete reference.
Method Specifications
Primary Introspection — Start Here
These are the entry points. Get the timeline, then drill down.
TIMELINE
The master view. Shows all events with timestamps, types, and IDs.
Input:
method:TIMELINEparameters:composer:string# Composer ID (@1, name fragment, hash)limit:int# How many events (default: 50)filter:string# Event type filter (thinking, tool, user, all)since:string# Time filter ("1 hour ago", event ID)
CONTEXT-FOCUS #142 — What went into context at that point?
THINKING #143 — Full text of that thinking block
TOOLS #144-148 — Tool calls in that range
EXPLAIN #149 — Why was that change made?
The timeline is the map. Everything else is zooming in.
CONTEXT-FOCUS
Analyze what went into the context window for a specific call. Shows the cursor state — what files, snippets, conversation, and rules were assembled.
Input:
method:CONTEXT-FOCUSparameters:composer:string# Composer IDevent_id:string# Optional: specific event (default: latest)
Process:
# Get context sources for a composer
cursor-mirror context-sources <composer>
# Analyze what was in context at a specific event
cursor-mirror timeline <composer> --before <event_id> --type context
The 🪟 tag marks context window analysis — showing what the LLM "saw" for this call.
THINKING
Show reasoning blocks for an event or range.
Input:
method:THINKINGparameters:composer:stringevent_id:string# Specific eventrange:string# Or range like "143-146"
Process:
cursor-mirror thinking <composer> --event <id>
Output:
🤔💭 🧠 Thinking Block #143
"I need to understand the current structure of the auth module before
making changes. Let me read the session handling code first.
The user mentioned a race condition — I should look for any async
operations that might not be properly awaited. Common patterns to
check: cookie operations, token refresh, database calls..."
(247 chars, 16:46:18)
TOOLS
Show tool calls for an event or session.
Input:
method:TOOLSparameters:composer:stringevent_id:string# Specific event, or omit for alltool_filter:string# Filter by tool name (Read, Write, Shell, etc.)
method:COMMITparameters:files: [string] # Files to commit (or '.' for all)summary:string# What changed (auto-detect if omitted)include_thinking:bool# Link to cursor-mirror (default: true)style:enum# technical (default) | changelog | pr | burke
Styles:
Style
Use
Output
technical
Default. Concise, factual
fix: race condition in auth + bullets
changelog
Release notes
User-facing changes grouped by type
pr
Pull request body
Summary, changes, test plan
burke
James Burke storytelling
Facet-to-facet connections, disco ball
Process:
Stage specified files (git add)
Gather context from conversation
If include_thinking, query cursor-mirror for recent events
method:EXPLAINparameters:commit:string# Commit hash (full or abbreviated)
Process:
Get commit details (git show --format=...)
Extract timestamp
Search cursor-mirror for events around that time
Find the git commit tool call
Trace back to thinking blocks and user request
Output:
commit_message:"Incarnation Ceremony: ..."timestamp:"2026-01-15T19:30:00Z"author:"Coherence Engine"user_request:"Incarnate the kittens with emoji souls"thinking_blocks:-event_id:141content:"I need to invoke INCARNATION protocol..."-event_id:142content:"Myrcene's terpene is sedating..."tool_calls:-event_id:144tool:write_fileargs: {path:"kitten-myrcene/CHARACTER.yml"}
-event_id:148tool:git_commitargs: {message:"..."}
method:HISTORYparameters:path:string# File or directorydepth:int# Number of commits (default: 10)include_thinking:bool# Include cursor-mirror links (default: true)
Process:
Get git log for path (git log -n <depth> --format=... -- <path>)
For each commit, attempt to find cursor-mirror link
Build narrative timeline
Output:
timeline:-commit:"abc123"date:"2026-01-15"message:"Incarnation Ceremony: ..."thinking_link:"cursor-mirror://..."summary:"Kittens received emoji souls"-commit:"def456"date:"2026-01-14"message:"Initial character creation"thinking_link:nullsummary:"Created basic character files"
DEEP-COMMIT
Technical analytics mining — extract quantitative metrics from cursor-mirror and git.