autoskill

This skill analyzes coding sessions to extract durable preferences from corrections and approvals, then proposes targeted updates to Skills that were active during the session. It acts as a learning mechanism across sessions, ensuring Claude improves based on feedback.

The user triggers autoskill after a session where Skills were used. The skill detects signals, filters for quality, maps them to the relevant Skill files, and proposes minimal, reversible edits for review.

## Session scope

By default, analyze only the **current session** (from SessionStart to now). This ensures fresh, relevant feedback without noise from old sessions.

To analyze patterns across multiple sessions, user must explicitly request: "analyze my last 5 sessions" or "look for patterns across this week".

## When to activate

Trigger on explicit requests:

- "autoskill", "learn from this session", "update skills from these corrections"
- "remember this pattern", "make sure you do X next time"

Do NOT activate for one-off corrections or when the user declines skill modifications.

## Where to apply changes

Distinguish between skill-specific behavior and project-wide conventions:

**Update Skills when:**

- Signal relates to how a specific skill should behave
- Preference affects skill trigger conditions or outputs
- Pattern is about the skill's decision-making process

**Update CLAUDE.md when:**

- Project-wide conventions (naming, file structure, architecture)
- Tool/library preferences that span multiple skills
- Team style preferences (spacing, comments, error handling)
- Domain-specific terminology used across the codebase

**Example:**

- "Don't add error handling for internal functions" → code-simplifier skill (how to simplify)
- "We use `cn()` utility for className merging" → CLAUDE.md (project convention)
- "Auth logic lives in middleware, not components" → CLAUDE.md (architecture decision)

## Signal detection

Scan the session for:

**Corrections** (highest value)

- "No, use X in