Menu
Analyzes staged git changes and evaluates agentic context files (Claude, Codex, Cursor, etc.) to suggest additions or removals. Use after staging changes before committing.
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.
Basé sur la classification professionnelle SOC
Use when the user wants to start or stop recording a branch decision trail, record a decision and its rationale, or show and audit the rationale behind a branch or PR. Invoke as /logic toggle, /logic track, or /logic show. Captures decisions across concurrent worktrees, validates evidence, and can add a reviewable trail to a PR.
Use when the user wants to establish a brand or personal writing voice, brainstorm content ideas, hone a content thesis, write platform-native posts for Blog, LinkedIn, Reddit, or X, or modify an existing post for another platform. Creates and reads VOICE.md, researches current platform guidance, fact-checks claims, and outputs social posts under social/<proposal-slug>/.
Security audit and active remediation for agent skills. Analyzes SKILL.md instructions and bundled scripts for prompt injection, data exfiltration, excessive permissions, supply chain risks, and other threats. Presents findings inline, optionally generates reports, and can rewrite skills to remove security concerns.
Explore and analyze TUI applications to document their features for cloning. Use when asked to reverse-engineer, analyze, document, or understand a terminal UI like Claude Code, OpenCode, Codex, lazygit, or any ratatui/ncurses-based application. Launches the target TUI in tmux, systematically explores all views and keybindings, captures ASCII diagrams of each screen, and writes findings incrementally to a markdown file (survives context compaction).
Conducts time-boxed technical investigations, competitive research, or feasibility analysis. Asks clarifying questions upfront and produces a structured markdown report with executive summary. Use for technical spikes, architecture decisions, or evaluating new technologies.
| name | context-curation |
| description | Analyzes staged git changes and evaluates agentic context files (Claude, Codex, Cursor, etc.) to suggest additions or removals. Use after staging changes before committing. |
Analyze staged git changes and evaluate whether agentic context files need to be updated to reflect those changes.
This skill scans for agentic context files across multiple platforms:
| Platform | Locations |
|---|---|
| Claude Code | .claude/, CLAUDE.md |
| Codex | .codex/, codex.md |
| Cursor | .cursor/, .cursorrules |
| Aider | .aider/, .aider.conf.yml |
| GitHub Copilot | COPILOT.md, .github/copilot-instructions.md |
| Generic | AGENTS.md, AI.md, CONTEXT.md |
| Project docs | docs/, README.md (architecture sections) |
Run git diff --staged to understand what's being committed:
Locate all agentic context files in the repository and extract:
Cross-reference staged changes against existing context:
Produce actionable suggestions with clear rationale.
For each suggested addition:
## ADD: [Brief description]
**Context file**: [path to file that should be updated]
**Rationale**: [Why this should be documented]
**Suggested content**:
[Proposed text to add]
**Evidence from staged changes**:
- [file:line] - [relevant code snippet or change]
For each suggested removal:
## REMOVE: [Brief description]
**Context file**: [path to file containing outdated content]
**Current content**: [text that should be removed or updated]
**Rationale**: [Why this is now stale]
**Evidence from staged changes**:
- [file] - [deleted or changed code that invalidates this]
If context files are already aligned with staged changes:
## Context files are up to date
Reviewed [N] context files against staged changes.
No updates recommended.
git diff --staged --stat to get an overview of staged changesgit diff --staged to examine the actual changes in detail