change-classificationlisted

# Change Classification Domain skill for analyzing and classifying code changes before committing. ## Iron Law **CLASSIFY BEFORE COMMITTING. Every changed file gets a classification. Unclassified files do not get staged.** Committing without classification is how out-of-context changes, secrets, and unintended modifications reach the repository. ## Classification Algorithm For each changed file, evaluate signals to classify as: **in-context**, **uncertain**, or **out-of-context**. ### Primary Signals (Strong) | Signal | Classification | Detection | |--------|---------------|-----------| | File already in branch diff | in-context | `git diff --name-only $DEFAULT_BRANCH...HEAD` includes file | | File matches issue keywords | in-context | File path contains words from issue title/body | | File in active task | in-context | File path matches TaskList task descriptions | | File matches task directory | in-context | Same top-level directory as task-related files | ### Secondary Signals (Supporting) | Signal | Classification | Detection | |--------|---------------|-----------| | Same directory as other changes | lean in-context | Sibling of already-classified in-context file | | Test file for changed module | lean in-context | Naming convention match (e.g., `foo.rb` → `foo_test.rb`) | | Config in project root | uncertain | Changes to dotfiles, config, package manifests | | Unrelated directory | out-of-context | No connection to issue or tasks | ### Red Flags These always