vestige

Scan code for TODO/FIXME comments and maintain an issue registry.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Niraven/pokee-deep-research-skill --skill vestige
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vestige
Source: https://github.com/Niraven/pokee-deep-research-skill/tree/main/skills/vestige
Command: npx skills add https://github.com/Niraven/pokee-deep-research-skill --skill vestige

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers and teams identify, track, and manage technical debt and legacy code within their projects, preventing the accumulation of unmaintainable systems.

Core Features & Use Cases

  • Track Deprecated Code: Monitor and flag code that is no longer actively supported or recommended.
  • Identify TODO/FIXME Comments: Automatically find and list comments indicating areas needing future attention or refactoring.
  • Manage Known Issues: Maintain a record of existing bugs or limitations in the codebase.
  • Target Refactoring Efforts: Pinpoint specific sections of code that require modernization or improvement.
  • Use Case: A team can use this Skill to get a consolidated view of all technical debt items before planning their next sprint, ensuring they allocate resources effectively to maintain code health.

Quick Start

Use the vestige skill to list all known issues in the current project.

Frequently Asked Questions about vestige

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

FAQPage Schema
How do I track technical debt and legacy code in my software project?

To track technical debt and legacy code, this Skill scans for specific comment patterns like TODOs and FIXMEs, maintains an issue registry for known bugs, and flags deprecated components to consolidate maintenance priorities.

How do I find and list TODO and FIXME comments for code refactoring?

Finding TODO and FIXME comments is handled by scanning the codebase for specific comment patterns, listing areas needing future attention, and identifying them as primary refactoring targets for maintenance.

What is the best way to manage deprecated code and known issues before a sprint?

Managing deprecated code and known issues before a sprint requires a consolidated view of technical debt items, enabling teams to allocate refactoring resources effectively and maintain code health.

How do I identify refactoring targets in a legacy codebase?

Identifying refactoring targets in a legacy codebase involves tracking deprecated components, scanning for outstanding issues, and pinpointing specific sections of code that require modernization.

Are there prerequisites for scanning a codebase to manage technical debt?

Scanning a codebase to manage technical debt requires no external dependencies, relying solely on scanning for specific comment patterns and maintaining an internal issue registry to track maintenance priorities.

Can I use this to maintain a registry of existing bugs and limitations?

Yes, you can maintain a record of existing bugs and limitations by using the issue registry feature, which tracks known issues alongside deprecated code and technical debt items.