665,000+ skills indexed

popoffvgCOMMUNITY

Explore all skills by this author →

Verified:𝕏@vg_popoff GitHub

todo-fix

Detect TODO, FIXME, HACK, and XXX markers in Git diffs and untracked files.

2|1|Updated Apr 10, 2023

Search Tags:#todo #static-analysis #code-review #git-diff #marker #untracked-files

One-click install

npx skills add https://github.com/popoffvg/dotfiles --skill todo-fix

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: todo-fix
Source: https://github.com/popoffvg/dotfiles/tree/main/skills/todo-fix
Command: npx skills add https://github.com/popoffvg/dotfiles --skill todo-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers identify and surface actionable TODO, FIXME, HACK, or XXX markers in code changes and untracked files to prevent important tasks from being forgotten before commits.

Core Features & Use Cases

Detects markers in git diffs (staged and unstaged) and in untracked files.
Presents results in a structured table with File, Line, Marker, and Text to facilitate quick remediation.
Supports categorization by marker type and prioritization for code reviews and PR preparation.

Quick Start

Run the todo-fix scan on your repository to surface all actionable markers.

Frequently Asked Questions about todo-fix

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

FAQPage Schema

How do I find TODO markers in my git diff before committing?▼

To find TODO markers in a git diff, scan staged and unstaged changes to surface actionable TODO, FIXME, HACK, and XXX flags. This produces a tabular summary with file, line, marker, and text to prevent tasks from being forgotten before commits.

Can I detect FIXME and HACK markers in untracked files?▼

You can detect FIXME and HACK markers in untracked files by scanning the entire worktree for actionable markers. It identifies these flags in new files not yet tracked by git, ensuring code reviews capture all pending tasks.

What is the best way to scan code changes for TODO comments during PR preparation?▼

Scanning code changes for TODO comments during PR preparation involves analyzing git diffs to categorize markers by type and severity. This structured approach surfaces all actionable items in a concise table for quick remediation.

Does this static analysis tool work with both staged and unstaged git changes?▼

This static analysis tool works with both staged and unstaged git changes, scanning the full diff range. It identifies TODO, FIXME, HACK, and XXX markers across all active modifications and untracked files.

How are the detected TODO and FIXME markers categorized for code review?▼

Detected TODO and FIXME markers are categorized by marker type and severity for code review. The scan outputs a structured table containing the file, line number, marker type, and text, facilitating quick prioritization and remediation.

Related Skills

Explore More Software Engineering Skills→

codex-review

Review Git branch diffs and staged changes for code issues.

tech-debt

Scan codebases for quality issues and generate GitHub tracking issues.

orient

Diagnose repository state and summarize the current working context.

document-release

Synchronize markdown documentation with shipped code changes via git diffs.