analysis-provenance

Solid

Identify code ownership before modifying validators or linters. Checks file headers for provenance indicators, reviews documentation, and determines provenance as UPSTREAM, LOCAL, VENDOR, or UNKNOWN. Prevents accidental modification of upstream tools.

AI & Automation 42 stars 13 forks Updated today MIT

Install

View on GitHub

Quality Score: 80/100

Stars 20%

Recency 20%

100

Frontmatter 20%

Documentation 15%

100

Issue Health 10%

License 10%

100

Description 5%

100

Skill Content

# 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...

Details

Author: rjmurillo
Repository: rjmurillo/ai-agents
Created: 8 months ago
Last Updated: today
Language: Markdown
License: MIT

Integrates with

Anthropic · AI

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Solid

test-provenance-guard

Detects tests that pass by construction — tests that define a private copy of the function under test instead of importing the production module — and self-heals by extracting the inline logic to an exported function, updating production callers, and rewriting the test to import the export. Two checks: (1) static — the test file must import the SUT and must not shadow its exported names; (2) mutation — blanking the production function body re-runs the test and expects failure. Runs autonomously inside autonomous-workflow Phase 4 and as a slash command for human-driven PR review. Use when adding new tests for existing or refactored code, when CI is green but you are unsure whether the tests actually exercise production, or when reviewing a PR for tests-by-construction. Triggers on "test provenance", "tests by construction", "verify tests cover real code", "tests duplicate logic", "mutation sanity check", "are these tests fake", "/test-provenance-guard".

8 Updated 2 days ago

mthines

AI & Automation Featured

manuscript-provenance

Computational provenance audit verifying every number, table, and figure in a manuscript derives from code, not manual entry. Triggers on: "check provenance", "verify reproducibility", "audit my pipeline", "are my numbers from code", "provenance audit". Companion to manuscript-review (prose audit).

313 Updated 4 days ago

Mathews-Tom

AI & Automation Solid

analyse

Analyze issue/PR/problem before implementation; produce source-backed findings and measurable gates.

25 Updated today

Borda