busya/ss-tools
1
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity
Files
d8df1fff594e994bfc80f06007cb81691e917900
ss-tools/.opencode/command/speckit.semantics.md
busya d8df1fff59 semantic cleanup
2026-05-08 10:07:05 +03:00

2.2 KiB
Raw Blame History

description
description
Maintain semantic integrity by reindexing, auditing, and reviewing the Rust MCP repository through AXIOM MCP tools.

User Input

$ARGUMENTS

You MUST consider the user input before proceeding (if not empty).

Goal

Ensure the repository adheres to the active GRACE semantic protocol using AXIOM MCP as the primary execution engine: reindex, measure semantic health, audit contracts, audit decision-memory continuity, and optionally route contract-safe fixes.

Operating Constraints

  1. ROLE: Orchestrator — coordinate semantic maintenance at the workflow level.
  2. MCP-FIRST — use AXIOM task-shaped tools for discovery, context, audit, impact analysis, and safe mutation planning.
  3. STRICT ADHERENCE — follow the local semantic authorities:
    • .kilo/skills/semantics-core/SKILL.md
    • .kilo/skills/semantics-contracts/SKILL.md
    • .kilo/skills/semantics-testing/SKILL.md
    • docs/SEMANTIC_PROTOCOL_COMPLIANCE.md
    • docs/adr/*
  4. NON-DESTRUCTIVE — do not remove business logic; only add or correct semantic markup unless the user requested implementation changes.
  5. NO PSEUDO-CONTRACTS — do not mechanically inject fake semantic boilerplate.
  6. ID NAMING — use short domain-driven IDs, never language import paths or filesystem-shaped IDs as the semantic primary key.
  7. DECISION-MEMORY CONTINUITY — audit ADRs, preventive task guardrails, and local @RATIONALE / @REJECTED as a single chain.

Execution Steps

  1. Reindex the semantic workspace.
  2. Measure workspace semantic health.
  3. Audit top issues:
    • broken anchors or malformed DEF regions
    • missing complexity-required metadata
    • unresolved relations
    • isolated critical contracts
    • missing ADR continuity
    • restored rejected paths
    • retained workaround logic lacking local decision-memory tags
  4. Build remediation context for the top failing contracts.
  5. If $ARGUMENTS contains fix or apply, route to an implementation/curation agent instead of applying naive text edits.
  6. Re-run audit and report PASS/FAIL.

Output

Return:

  • health metrics
  • PASS/FAIL status
  • top issues
  • decision-memory summary
  • action taken or handoff initiated