scip-query 0.19.5 → 0.19.6

package/skills/scip-twin-drift/SKILL.md

@@ -1,109 +0,0 @@
----
-name: scip-twin-drift
-description: Find and resolve twin drift with scip-query. Use for same-name or near-name functions across files with diverged bodies, drifted policy thresholds, one-sided fixes, or consolidating a duplicated concept into one canonical helper.
-commands:
-  - template: 'scip-query twin-drift --json --full'
-    when: 'Run the detector: every DIVERGENT and near-name group in scope.'
-  - template: 'scip-query duplicate-bodies --json --full'
-    when: "Cross-check: IDENTICAL groups are duplicate-bodies' job, not this skill's."
-  - template: 'scip-query code <symbol>'
-    when: "Classify a divergent group: read every member's body."
-  - template: 'scip-query refs <symbol>'
-    when: 'Pick the canonical twin: consumer count per member.'
-  - template: 'scip-query diff-gate --json'
-    when: 'Verify: the twin-partner check must not flag a one-sided fix.'
----
-
-# scip-twin-drift
-
-Use this skill when the same concept exists in more than one place under the same or a near-name (case-insensitive, or edit-distance ≤ 2 for names ≥ 8 characters) and the bodies have silently diverged. A twin drift group is a same-leaf-name family of callables spanning at least two files whose normalized-token bodies are neither identical (that is `duplicate-bodies`' job) nor unrelated (a homonym like `render` or `parse`) but partially overlapping — the signature of a concept that was copied once and then edited independently in only some of its copies.
-
-Load shared mechanics from [`../_shared/SKILL.md`](../_shared/SKILL.md).
-
-<!-- BEGIN GENERATED SKILL COMMANDS -->
-## Commands for this skill
-
-| Command | Purpose | Returns | Coverage | When |
-| --- | --- | --- | --- | --- |
-| `scip-query twin-drift --json --full` | Twin drift candidates: same-name (or near-name) functions across files with diverged bodies | twin symbol pairs, history, and divergence evidence | `bounded` | Run the detector: every DIVERGENT and near-name group in scope. |
-| `scip-query duplicate-bodies --json --full` | Find exact duplicate small-body candidates across files | callable groups with exact normalized-body identity | `bounded` | Cross-check: IDENTICAL groups are duplicate-bodies' job, not this skill's. |
-| `scip-query code <symbol>` | Read the source code for a symbol (bounded to its definition range) | definition identity, source, and line range | `complete` | Classify a divergent group: read every member's body. |
-| `scip-query refs <symbol>` | Find all files referencing a symbol | referencing file paths; reference line numbers grouped by file | `bounded` | Pick the canonical twin: consumer count per member. |
-| `scip-query diff-gate --json` | Gate the current diff: architecture regressions plus echo, migration, coordination, doc-drift, unused-param, and new-dead candidates; exit 1 on blocking findings | blocking findings with check id, message, and remediation; advisory findings; root-cause groups; changed file and symbol counts; process exit status (1 when blocking findings exist) | `bounded` | Verify: the twin-partner check must not flag a one-sided fix. |
-
-Use this shortlist first. Open [`../_shared/SKILL.md`](../_shared/SKILL.md) only when it is insufficient.
-<!-- END GENERATED SKILL COMMANDS -->
-
-## Rules
-
-1. `IDENTICAL` groups defer to `duplicate-bodies`; do not re-report them here.
-2. Homonyms (similarity below `--min-similarity`, default 0.3) are noise unless `--include-homonyms` was requested; do not chase them.
-3. Every `DIVERGENT` group in scope gets a classification before this skill reports done.
-4. Prefer consolidation to one exported helper over leaving parallel copies; when consolidation is unsafe or premature, record the intent gap explicitly (comment or waiver) rather than silently accepting drift.
-5. A twin-partner `diff-gate` finding on a change you are making is the live version of this same defect class — treat it as a signal to run this skill, not just to suppress.
-
-## Workflow
-
-### 1. Run the detector
-
-```bash
-scip-query twin-drift --json --full
-```
-
-Scope with `-s/--scope <path>` when the review is bounded to a module. Record group count, member count, and `maxDivergence` per group.
-
-This step is complete only when every group in scope is enumerated with its relationship (`divergent` vs suppressed homonym).
-
-### 2. Classify each DIVERGENT group
-
-For each group, read every member with `scip-query code <symbol-or-file:range>` and use the group's `firstDivergentTokens` as a starting point for where the bodies diverge. Classify the group as one of:
-
-- **Intentional variation**: the copies differ because the domains genuinely differ (for example a React-specific vs Vue-specific structural comparator that must branch on framework-specific overlap checks). Essential variation stays; record why.
-- **Drifted policy**: the copies encode what should be one policy (a threshold, a normalization rule, an edge-case guard) that only some copies received when it last changed. This is a bug: pick the correct value and propagate it, or extract the policy into one named function/constant.
-- **One-sided fix**: one copy was bugfixed or hardened and its twin(s) were not. This is also a bug: apply the same fix to every member, or consolidate.
-
-This step is complete only when every DIVERGENT group in scope has one of these three labels with a one-line reason.
-
-### 3. Pick the canonical twin and act
-
-For groups getting consolidated, pick the canonical member by consumer count:
-
-```bash
-scip-query refs <symbol-in-file-A>
-scip-query refs <symbol-in-file-B>
-```
-
-Prefer the member with the most consumers, or the one in the more general/shared location when counts tie. Extract or move the canonical body to one exported helper; update the other member(s) to call it, or delete them if they were pure duplication with different names for the caller's convenience. Preserve any classified-essential variation as a parameter or a thin caller-side branch, not as a second copy of the whole body.
-
-For groups marked intentional variation, do not force consolidation; record the reason in a comment near one of the members so the next `twin-drift` run and the next reader both see it was considered.
-
-This step is complete only when every DIVERGENT group is either consolidated (with the old copies gone or forwarding) or has a recorded reason it stays separate.
-
-### 4. Verify
-
-Rerun the detector to confirm consolidated groups no longer appear as DIVERGENT, then run the routed postchecks from `scip-verify` and:
-
-```bash
-scip-query diff-gate --json
-```
-
-The `twin-partner` check is advisory (it never blocks the gate by itself) but a finding here on your own diff means you just reproduced the exact defect class this skill exists to catch — fix or explicitly accept it before finishing.
-
-This step is complete only when `twin-drift` shows no unclassified `DIVERGENT` groups in scope and `diff-gate` findings are resolved or explained.
-
-## Report
-
-```markdown
-Scope:
-Groups found: N (M divergent, K suppressed homonyms)
-
-Divergent groups:
-
-- <leaf name> (<files>) — classification: intentional variation / drifted policy / one-sided fix
-  - action: consolidated into <canonical file:symbol> / reason kept separate
-
-Verification:
-
-- `scip-query twin-drift --json --full`: <result>
-- `scip-query diff-gate --json`: <result>
-```

package/skills/scip-twin-drift/agents/openai.yaml

@@ -1,4 +0,0 @@
-interface:
-  display_name: "SCIP Twin Drift"
-  short_description: "Find and resolve same-name twins that have silently diverged"
-  default_prompt: "Use scip-query twin-drift to find same-name or near-name functions that have diverged across files, classify each divergence, and consolidate or record the intent gap."

package/skills/scip-vue-maintainability/SKILL.md

@@ -1,107 +0,0 @@
----
-name: scip-vue-maintainability
-description: Review Vue maintainability with scip-query. Use for Vue, Nuxt, SFCs, duplicated templates, composable candidates, large views, frontend health pressure, or verifying Vue reuse after refactors.
-commands:
-  - template: 'scip-query augment-vue --project <path-to-tsconfig>'
-    when: 'Bound and augment: add compiler-resolved Vue SFC references first.'
-  - template: 'scip-query vue-component-duplicates --scope <scope> --full --json'
-    when: 'Scan: duplicated template structure candidates.'
-  - template: 'scip-query vue-composable-candidates --scope <scope> --full --json'
-    when: 'Scan: shared state/lifecycle extraction candidates.'
-  - template: 'scip-query vue-large-view-pressure --scope <scope> --full --json'
-    when: 'Scan: SFCs carrying several reasons to change.'
-  - template: 'scip-query recent-duplicates --scope <scope> --full --json'
-    when: 'Scan: recent code re-implementing established components.'
-  - template: 'scip-query health --json'
-    when: 'Scan: frontend health pressure baseline.'
----
-
-# scip-vue-maintainability
-
-Use this skill to review Vue frontends as maintainable systems of single-file components, templates, scripts, styles, external scripts, components, and composables.
-
-Load shared mechanics from [`../_shared/SKILL.md`](../_shared/SKILL.md).
-
-<!-- BEGIN GENERATED SKILL COMMANDS -->
-## Commands for this skill
-
-| Command | Purpose | Returns | Coverage | When |
-| --- | --- | --- | --- | --- |
-| `scip-query augment-vue --project <path-to-tsconfig>` | Add compiler-resolved Vue SFC references to the SQLite index using Volar | Vue augmentation counts, project, and diagnostics | `complete` | Bound and augment: add compiler-resolved Vue SFC references first. |
-| `scip-query vue-component-duplicates --scope <scope> --full --json` | Find heuristic duplicated Vue component structure candidates from template tags, bindings, slots, and directives | component pairs with structural similarity evidence | `bounded` | Scan: duplicated template structure candidates. |
-| `scip-query vue-composable-candidates --scope <scope> --full --json` | Find heuristic Vue composable extraction candidates from shared state, effects, requests, and template bindings | component groups and shared composable-shaped behavior | `bounded` | Scan: shared state/lifecycle extraction candidates. |
-| `scip-query vue-large-view-pressure --scope <scope> --full --json` | Find heuristic large Vue view pressure candidates from template, script, style, and external script line counts | view identities with size and responsibility pressure | `bounded` | Scan: SFCs carrying several reasons to change. |
-| `scip-query recent-duplicates --scope <scope> --full --json` | Directional duplicate candidates: recent code that re-implements established callable, React, or Vue code | recent and established symbol pairs with similarity evidence | `bounded` | Scan: recent code re-implementing established components. |
-| `scip-query health --json` | Composite codebase health report with prioritized action list | health score, findings, priorities, baselines, and coverage notes | `bounded` | Scan: frontend health pressure baseline. |
-
-Use this shortlist first. Open [`../_shared/SKILL.md`](../_shared/SKILL.md) only when it is insufficient.
-<!-- END GENERATED SKILL COMMANDS -->
-
-## Terms
-
-A Vue component duplicate candidate is a pair or group of rendered structures that repeat the same user-facing arrangement, controls, states, or data-presentation shape enough that a shared component may reduce drift.
-
-A Vue composable candidate is a pair or group of script behaviors that repeat the same state lifecycle, effects, requests, validation, persistence, or derived-data policy enough that a shared composable may preserve behavior better.
-
-Large view pressure means one SFC or linked view file contains several kinds of knowledge that change for different reasons.
-
-## Workflow
-
-### 1. Bound and augment
-
-Pick the narrowest Vue source root, feature area, or changed-file scope that still includes likely reuse partners. When component references, imported composables, script blocks, or linked external scripts matter, run:
-
-```bash
-scip-query augment-vue --project <path-to-tsconfig>
-```
-
-This step is complete only when the review scope and augmentation decision are recorded.
-
-### 2. Scan
-
-Run uncapped commands:
-
-```bash
-scip-query vue-component-duplicates --scope <scope> --full --json
-scip-query vue-composable-candidates --scope <scope> --full --json
-scip-query vue-large-view-pressure --scope <scope> --full --json
-scip-query recent-duplicates --scope <scope> --full --json
-scip-query health --json
-```
-
-This step is complete only when command scope, counts, and uncapped/full status are recorded.
-
-### 3. Cross-check candidates
-
-- Component duplicate only: inspect for shared presentational component or existing component reuse.
-- Composable candidate only: inspect for shared lifecycle, request, validation, persistence, event, or derived-state policy.
-- Both: inspect for a feature-level concept needing both component and composable boundaries.
-- Large view only: split by reason to change, not by line count.
-
-Use:
-
-```bash
-scip-query outline <file>
-scip-query deps <file>
-scip-query rdeps <file>
-scip-query similar-files --scope <scope>
-scip-query recent-duplicates --scope <scope> --full --json
-```
-
-This step is complete only when each top candidate is reuse, extract, split, skip, or blocked.
-
-### 4. Act and verify
-
-Prefer reuse before extraction. Extract components for repeated template structure, props, slots, states, or design-system composition. Extract composables for repeated state, lifecycle, requests, validation, persistence, derived data, or event policy. Keep essential variation at the call site.
-
-Invoke `scip-verify` and use its authoritative postcheck table, including the applicable Vue, extraction, duplicate, parameter, wrapper, passthrough, and stale-abstraction checks.
-
-The work is complete only when acted-on candidate pairs disappear, weaken materially, or are explicitly accepted as essential variation.
-
-## False Positive Checks
-
-Shared design-system primitives, CSS utilities, icons, labels, or test IDs are not enough. Similar templates with different domain lifecycles may justify a presentational component but not a composable. A large style block is pressure, not proof.
-
-## Report
-
-Report executive read, command evidence, candidate groups, recommended action, post-change proof, and remaining accepted variation.

package/skills/scip-vue-maintainability/agents/openai.yaml

@@ -1,4 +0,0 @@
-interface:
-  display_name: "SCIP Vue Maintainability"
-  short_description: "Review Vue reuse and view pressure"
-  default_prompt: "Use $scip-vue-maintainability to review Vue components, composables, views, and frontend health pressure."