titan-grind

Automate dead symbol adoption across codebases with graph queries and gate checks.

86|20|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/optave/ops-codegraph-tool --skill titan-grind
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: titan-grind
Source: https://github.com/optave/ops-codegraph-tool/tree/main/.claude/skills/titan-grind
Command: npx skills add https://github.com/optave/ops-codegraph-tool --skill titan-grind

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Titan Grind phase automates the identification and adoption of extracted dead symbols across a codebase, reducing noisy dead-code drift and aligning code with the evolving forge outputs.

Core Features & Use Cases

  • Identify candidate dead symbols introduced by forge phases and surface them for evaluation.
  • Classify dead helpers into adopt, re-export, promote, false-positive, intentionally-private, or remove, with per-target state persistence.
  • Wire approved helpers into existing consumers across multiple files, ensuring behavior remains semantically identical.

Quick Start

Invoke titan-grind to process the next forge phase and report progress.

Frequently Asked Questions about titan-grind

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate the removal of dead code after refactoring helpers?

Automating dead code removal after refactoring involves identifying extracted dead symbols and wiring legitimate adopters into consumers. This process uses graph queries and diffs to classify dead helpers, ensuring safe, semantically identical transformations across the codebase.

What is the best way to classify dead symbols during a codebase refactor?

Classifying dead symbols during a codebase refactor involves categorizing extracted helpers into adopt, re-export, promote, false-positive, intentionally-private, or remove. This classification uses per-target state persistence to track and safely process each symbol during the grind phase.

How do I wire extracted helpers into existing consumers across multiple files?

Wiring extracted helpers into existing consumers requires analyzing code changes and applying gate checks to ensure semantic equivalence. The process automatically connects approved helpers across multiple files, maintaining behavior while eliminating dead code drift from forge outputs.

Does automated dead symbol adoption support resumable transformations?

Automated dead symbol adoption supports resumable transformations through per-target state persistence. This strict process tracks each target's classification and adoption status, allowing the grind phase to safely resume if interrupted during codebase refactoring.

When do I need to run a codegraph analysis for dead code elimination?

Codegraph analysis for dead code elimination is needed during grind phases following forge commits. When extracted helpers create dead symbols across a codebase, graph queries and diffs identify candidates for adoption or removal to reduce noisy dead-code drift.