scip-query 0.10.12 → 0.11.0

package/skills/scip-adoption/SKILL.md

@@ -1,122 +0,0 @@
----
-name: scip-adoption
-description: Adopt scip-query in a repository from first run through verified local readiness. Use when the user wants to install, bootstrap, onboard, set up, refresh, or roll out scip-query in a project, including skills, indexers, local capabilities, health dossier, and post-setup cleanup handoff.
----
-
-# SCIP Adoption
-
-Use this skill when a repository needs to become a reliable scip-query workspace. A scip-query workspace is a source repository with a current SCIP index, runnable language indexers, installed agent skills, project guidance, and health evidence that agents can use before editing.
-
-## Rules
-
-1. Make local setup reliable before recommending cleanup.
-2. Do not run `scip-query setup-ci` in the default adoption path. CI is a separate explicit workflow.
-3. Treat missing capabilities as unavailable evidence, not as clean results.
-4. After setup, tell the user the health score and confirmed issue list before application-code cleanup begins.
-
-## Adoption Workflow
-
-### 1. Establish the project
-
-```bash
-pwd
-git rev-parse --show-toplevel
-scip-query --version
-```
-
-If `scip-query` is not available, install or link the package through the repo's package manager, then rerun the checks.
-
-### 2. Install skills and run setup
-
-```bash
-scip-query install-skills
-scip-query setup-hooks --json
-scip-query setup --json
-```
-
-Use `scip-query setup --git-hook --json` only when the user wants the local Git pre-commit diff-gate hook. Do not treat that hook as a replacement for final verification.
-Use `scip-query setup-hooks --json` when hook config needs to be repaired for the current repository without rerunning the full setup pass.
-
-### 3. Resolve blockers
-
-If setup reports `blocked` or `partial`, inspect dependencies and capabilities:
-
-```bash
-scip-query check-deps
-scip-query doctor
-scip-query capability-matrix --json
-scip-query status --capabilities
-```
-
-Fix missing indexers, toolchain dependencies, invalid config, or stale indexes. If a toolchain cannot be installed safely, record exact manual commands and keep the adoption state blocked.
-
-### 4. Initialize or validate config
-
-```bash
-scip-query init
-scip-query config-validate
-```
-
-Run `init` only when `.scipquery.json` is absent and the project needs config. Keep config minimal and evidence-backed. Use suppressions only for accepted findings with specific reasons:
-
-```bash
-scip-query suppress <id> --reason "<specific reason>"
-scip-query config-validate
-```
-
-### 5. Prove ongoing local usefulness
-
-```bash
-scip-query status --capabilities
-# If freshness is stale, missing, or unknown:
-# scip-query reindex
-scip-query stats
-scip-query files <known-source-term>
-scip-query outline <known-source-file>
-scip-query health --json --full
-scip-query diff-gate --json
-```
-
-Use `scip-query watch` only for an active local work session where automatic reindexing is useful. Do not leave it running as a hidden setup side effect.
-
-### 6. Hand off to health audit
-
-Invoke `scip-health-audit` after setup if the user wants cleanup or a perfect-code pass. The first user-facing message after the audit must include:
-
-- health score;
-- confirmed items that need attention;
-- unconfirmed signals;
-- unavailable or blocked checks;
-- recommended first cleanup batch.
-
-Then start cleanup only if the current request already asks for cleanup or the user approves the batch.
-
-## Adoption Report
-
-End with:
-
-```markdown
-Adoption: ready/partial/blocked
-
-Installed:
-- skills, hooks, indexers, config files, guidance files
-
-Capabilities:
-- available checks
-- unavailable checks and why
-
-Health:
-- score
-- dossier path
-- confirmed cleanup queue or audit handoff
-
-Verification:
-- `scip-query status --capabilities`, then `scip-query reindex` only if freshness is `stale`, `missing`, or `unknown`
-- `scip-query diff-gate --json`
-- targeted smoke commands
-
-Deferred:
-- CI setup, external toolchains, product decisions, or blocked checks
-```
-
-Do not claim adoption is ready until the index is current, core commands smoke-test, and `scip-query diff-gate --json` passes.

package/skills/scip-adoption/agents/openai.yaml

@@ -1,4 +0,0 @@
-interface:
-  display_name: "SCIP Adoption"
-  short_description: "Adopt scip-query in a repository"
-  default_prompt: "Set up scip-query in this repository, verify local capabilities, write the health dossier, and hand off confirmed cleanup work."

package/skills/scip-ai-cleanup/SKILL.md

@@ -1,153 +0,0 @@
----
-name: scip-ai-cleanup
-description: Clean up AI-generated code rot using scip-query's change-graph and verification tooling. Finds recent re-implementations of established code, drifting standards docs, speculative parameters, hidden coupling, and produces compiler-verified deletion plans. Sets up the CI ratchet so findings never regress.
----
-
-# AI-Generated Code Cleanup with scip-query
-
-AI-assisted development rots a codebase in specific, detectable ways: agents
-re-implement helpers they didn't know existed, leave half-wired parallel
-implementations behind, add parameters "for later" that never come, and the
-standards docs written FOR agents drift away from the code — so the next agent
-implements against a dead spec. None of this is visible in a single file;
-all of it is visible in the reference graph + the git change graph.
-
-This skill runs the full sweep and ends with a compiler-verified deletion
-plan and a CI ratchet.
-
-## When to Use This Skill
-
-- "Clean up the AI slop in this repo"
-- "Did the agents duplicate code?"
-- "Are our standards docs stale?"
-- "What can we safely delete?"
-- "Set up a quality gate for agent-written code"
-
-## Hard Rules
-
-1. **Evidence first.** Run `scip-query status --capabilities`; reindex only when freshness is `stale`, `missing`, or `unknown` before
-   trusting graph facts. All detectors print whether they're heuristic.
-2. **Verify before deleting.** Findings are candidates; only
-   `cleanup-plan --verify` output stamped COMPILER-VERIFIED is proof.
-   A FAILED verification is signal too — its errors name the references the
-   static evidence missed. Never delete on a failed batch.
-3. **Echoes consolidate INTO the established side.** When recent code
-   duplicates older code, extend the original and delete the echo — not the
-   reverse. The established side has the consumers and the bug-fix history.
-4. **Fix the doc or delete the doc — never leave it lying.** A stale standards
-   doc actively misleads every agent that reads it.
-
-## The Sweep
-
-### Step 1: Recent re-implementations (echoes)
-
-```bash
-scip-query recent-duplicates --window 100
-```
-
-- `ECHO` — recent code duplicating established code. Read both sides, then
-  migrate the echo's callers to the established symbol and delete the echo.
-- `TWIN` — both sides landed recently (often one agent session duplicating
-  itself). Pick the better-placed one, consolidate before they diverge.
-- Widen `--window` on slow-moving repos; narrow it right after a big agent
-  session.
-
-### Step 2: Drifting and lying docs
-
-```bash
-scip-query doc-drift
-scip-query doc-drift AGENTS.md     # detail mode for one doc
-```
-
-- `BROKEN REFERENCE` lines are the worst class: the doc cites files that no
-  longer exist. Fix those citations first.
-- `referenced by doc` subjects changed after the doc's last update — re-read
-  the subject files and update the doc's claims (or delete the doc).
-- Re-run after updating: staleness should drop to 0 for the docs you touched.
-
-### Step 3: Speculative generality
-
-```bash
-scip-query unused-params
-```
-
-Trailing parameters no body uses — already scoped to removals that are
-type-safe by construction (TS/JS, trailing-only, no parameter properties).
-Drop the parameters and any arguments at call sites.
-
-### Step 4: Hidden coupling
-
-```bash
-scip-query co-change
-```
-
-File pairs that repeatedly change in the same commits with NO dependency
-edge: hand-synchronized artifacts (schema ↔ inventory doc ↔ generator
-script, backend schema ↔ frontend store, .env.example ↔ env parser).
-For each pair, either name the shared concept in code (one source of truth)
-or add a contract test that fails when one side changes without the other.
-
-### Step 5: Compiler-verified deletion
-
-```bash
-scip-query cleanup-plan --verify --json
-```
-
-- Batches are ordered: batch 0 is graph-fact dead now; batch n is dead once
-  batch n-1 lands (the cascade). Apply ONE batch at a time.
-- `COMPILER-VERIFIED` means the deletion was applied in a throwaway worktree
-  and your own checker (tsc / cargo check / go build / ruff) passed differentially.
-- `FAILED` errors name real references — usually barrel export lines or
-  imports that must be removed together with the symbol, occasionally a
-  detector false positive. Investigate before deleting anything.
-- The `blocked` list explains why candidates can't cascade (e.g. a spec file
-  still references them).
-
-Apply only compiler-verified batches:
-
-```bash
-scip-query cleanup-apply --verified --batch 0
-```
-
-Use `--all` only after explicit human approval. Use `--force-dirty` only when
-you have inspected the touched files and know the existing edits are unrelated
-to the cleanup batch.
-
-### Step 6: Ratchet it
-
-```bash
-scip-query health --write-baseline   # commit .scipquery-baseline.json
-scip-query health --baseline         # exit 1 on any NEW finding — wire into CI
-scip-query diff-gate --json          # per-diff gate: echoes, missing partners, uncited docs
-```
-
-`diff-gate` is the leading indicator: run it on every agent commit / PR
-(`--base origin/main` in CI). Each finding carries a remediation the agent
-can apply directly.
-
-After each cleanup round, re-run `--write-baseline` to ratchet the count
-down. The gate is "don't get worse" — objective and ungameable.
-
-## Before Writing New Code (prevention)
-
-Tell implementing agents to run these BEFORE writing a helper or reading a
-standard:
-
-```bash
-scip-query plan-context <symbol-or-file>   # structure + HISTORY (churn, co-change partners)
-scip-query similar <new-function-name>     # does this already exist?
-scip-query doc-drift <standard.md>         # is the standard I'm about to follow stale?
-```
-
-The HISTORY section of plan-context lists the files that usually change with
-the target — the edit checklist that prevents the drift this skill cleans up.
-
-## Reporting
-
-End with a prioritized summary:
-
-1. Echoes/twins consolidated (LOC removed, callers migrated)
-2. Docs fixed vs deleted (staleness before → after)
-3. Compiler-verified deletions applied (LOC, batches)
-4. Hidden couplings resolved (named mechanism or contract test added)
-5. Baseline ratcheted: N findings → M

package/skills/scip-ai-cleanup/agents/openai.yaml

@@ -1,4 +0,0 @@
-interface:
-  display_name: "SCIP AI Cleanup"
-  short_description: "Clean up AI-generated code rot"
-  default_prompt: "Use $scip-ai-cleanup to find and fix AI-generated duplication, partial migrations, and stale cleanup fallout."