skills.rest
jlissner
jlissnerCOMMUNITY
Explore all skills by this author →
GitHub

grimoire-refactor

Identify and prioritize technical debt across codebase modules with fingerprinting and status tracking.

Updated Jan 26, 2025
Search Tags:#planning#refactor#code-quality#software-engineering#tech-debt#grimoire#debt-register
One-click install
npx skills add https://github.com/jlissner/lissner.io --skill grimoire-refactor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: grimoire-refactor
Source: https://github.com/jlissner/lissner.io/tree/main/.claude/skills/grimoire-refactor
Command: npx skills add https://github.com/jlissner/lissner.io --skill grimoire-refactor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematically identify and prioritize technical debt across a codebase, enabling focused refactoring and better planning.

Core Features & Use Cases

  • Provides a structured debt register with fingerprints, statuses, causes, and changes to guide triage.
  • Integrates with the grimoire pipeline (draft → plan → apply) to turn insights into concrete changes.
  • Supports prioritized remediation across hotspots, structural bloat, and duplication.

Quick Start

Run a guided debt triage session to generate a prioritized backlog of refactor items.

Frequently Asked Questions about grimoire-refactor

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

FAQPage Schema
How do I identify and prioritize technical debt across a codebase?▼

To identify technical debt, you scan codebase modules for hotspots, bloat, and duplication. This Skill systematically prioritizes debt items using a structured register with fingerprints, statuses, causes, and change linkage to drive focused refactoring and planning.

What is a debt register and how does it help with code refactoring?▼

A debt register is a structured backlog tracking technical debt items with fingerprints, statuses, causes, and change linkage. It guides triage by linking debt causes to concrete changes, enabling prioritized remediation across hotspots, structural bloat, and duplication within a codebase.

How do I run a guided triage session to generate a prioritized refactor backlog?▼

You run a guided debt triage session to generate a prioritized backlog of refactor items. The session scans modules for hotspots, bloats, and duplications, then defines debt items with fingerprints, statuses, causes, and change linkage for systematic remediation planning.

Can I integrate technical debt tracking into an existing software engineering pipeline?▼

Yes, technical debt tracking integrates with the grimoire pipeline through draft, plan, and apply stages. This workflow turns scanned debt insights into concrete changes, linking identified hotspots and bloats directly to implementation and planning actions.

What's the best way to track the status and causes of technical debt items?▼

The best way to track technical debt items is using a structured register with fingerprints, statuses, causes, and change linkage. This format enables rigorous status tracking and links each debt item to specific code changes for focused remediation.

Related Skills

Explore More Software Engineering Skills→
nikhillinitnikhillinit

tech-debt-tracker

Detect and prioritize technical debt with configurable thresholds and SQALE metrics.

Community
Advanced
jerelvelardejerelvelarde
6

manage-tech-debt

Track and prioritize technical debt in a codebase register.

Community
Advanced
Nuwanda04Nuwanda04

Tech Debt Tracker

Analyze codebases for technical debt using AST parsing and regex patterns.

Community
Advanced
CarlosQ96CarlosQ96

tech-debt

Scan codebases for debt indicators and generate a prioritized risk register.

Community
Advanced