skills.rest
tailcallhq
tailcallhqOFFICIAL
Explore all skills by this author →
Website𝕏@tailcallhqGitHub

resolve-fixme

Locate FIXME comments, expand multiline blocks, implement changes, and verify none remain.

7.5k|1.4k|Updated Dec 8, 2024
Search Tags:#automation#verification#discovery#code-quality#fixme#multi-file#code-refactor
One-click install
npx skills add https://github.com/tailcallhq/forgecode --skill resolve-fixme
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: resolve-fixme
Source: https://github.com/tailcallhq/forgecode/tree/main/.forge/skills/resolve-fixme
Command: npx skills add https://github.com/tailcallhq/forgecode --skill resolve-fixme

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires rg, python3, grep, and includes scripts (resource) components.

What problem does it solve?

This Skill helps identify and fully implement FIXME comments scattered across a codebase, turning scattered notes into concrete, production-ready changes and ensuring code quality by eliminating dangling TODOs.

Core Features & Use Cases

  • Discovery & Expansion: locate FIXME comments, expand multiline blocks to reveal the full instruction.
  • Consolidation & Planning: group related FIXMEs across files into a single implementation task.
  • Implementation & Verification: apply code changes, remove FIXMEs only after completion, and verify that no FIXMEs remain.

Quick Start

Run the discovery script to locate all FIXMEs, expand blocks, consolidate tasks, implement changes, and verify that no FIXMEs remain.

Frequently Asked Questions about resolve-fixme

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

FAQPage Schema
How do I automate resolving FIXME comments scattered across multiple files in my codebase?▼

To automate resolving FIXME comments across multiple files, you run a discovery workflow that locates all FIXMEs, expands multiline instruction blocks, groups related tasks into single implementations, applies code changes, and verifies no FIXMEs remain.

What is the best way to consolidate and implement grouped FIXME tasks across a repository?▼

The best way to consolidate FIXME tasks is using an automated workflow that groups related FIXMEs across files into a single implementation task, performs the required code refactoring, removes the FIXMEs only after completion, and verifies that none remain.

Does this FIXME resolution workflow require specific dependencies like ripgrep or python3?▼

Yes, this FIXME resolution workflow requires python3, rg, and grep to run its discovery scripts. These dependencies locate FIXME comments, expand multiline blocks, and verify that no FIXMEs remain across the repository.

Can I use this automated FIXME discovery and resolution process on any repository?▼

Yes, you can use this automated FIXME discovery and resolution process on any repository. The workflow coordinates discovery, planning, implementation, and verification steps end-to-end to eliminate dangling TODOs and ensure code quality.

Why are my FIXME comments not being removed even after making code changes?▼

FIXME comments are not removed until the associated code changes are fully implemented and verified. The workflow ensures FIXMEs are only deleted after completing the implementation task and confirming that no FIXMEs remain in the codebase.

Related Skills

Explore More Software Engineering Skills→
massgenmassgen
1.1k

file-search

Locate text and structural code patterns across large codebases using ripgrep and ast-grep.

Official
Basic
xxihxxih
1

laravel-verification

Verify Laravel projects for configuration, code quality, testing, security, and deployment readiness.

Community
Advanced
tcfialhotcfialho

nexus_review

Execute tests and static analyzers to validate software pipelines.

Community
Advanced
manastalukdarmanastalukdar
1

fix-todos

Resolve TODO, FIXME, HACK, and XXX comments using context-aware strategies.

Community
Advanced