analysis-provenancelisted

# Analysis Provenance Identify code ownership before modifying validators, linters, or tool configurations. ## Triggers - `check provenance before modifying` - `is this file upstream or local` - `who owns this validator` - `check code ownership` - `analyze provenance` --- ## Quick Start ```bash # Check provenance of a single file python3 .claude/skills/analysis-provenance/scripts/check_provenance.py --target .config/markdownlint.json # Check provenance of a directory python3 .claude/skills/analysis-provenance/scripts/check_provenance.py --target .config/ # JSON output for automation python3 .claude/skills/analysis-provenance/scripts/check_provenance.py --target PSScriptAnalyzerSettings.psd1 --format json ``` --- ## Quick Reference | Category | Meaning | Action | |----------|---------|--------| | **UPSTREAM** | External dependency (npm, pip, NuGet) | Configure, do not modify | | **LOCAL** | Project-owned code | Modify as needed | | **VENDOR** | Copied/vendored upstream code | Avoid modification, track upstream | | **UNKNOWN** | Cannot determine | Investigate before modifying | --- ## When to Use Use this skill **before**: - Modifying any validator or linter behavior - Changing tool configuration files - Investigating unexpected validation failures - Updating analyzer settings --- ## Process ```mermaid graph TD A[Target file or directory] --> B["1. Target Resolution<br/>Resolve paths, check exists"] B --> C["2. Directory Analysis<br/>node_modules, .ven