skills.rest
ethereum-optimism
ethereum-optimismOFFICIAL
Explore all skills by this author →
Website𝕏@optimismGitHub

fix-todo

Reopen closed GitHub issues referenced in TODO comments after CI failures.

6.5k|4.0k|Updated Feb 6, 2020
Search Tags:#automation#debugging#github actions#issue management#todo#ci
One-click install
npx skills add https://github.com/ethereum-optimism/optimism --skill fix-todo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fix-todo
Source: https://github.com/ethereum-optimism/optimism/tree/main/.claude/skills/fix-todo
Command: npx skills add https://github.com/ethereum-optimism/optimism --skill fix-todo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, curl, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automatically addresses failures in the TODO checker CI job by reopening GitHub issues that are still referenced by TODO comments in the codebase.

Core Features & Use Cases

  • Automated Issue Reopening: Reopens GitHub issues that were closed but are still flagged by the TODO checker.
  • CI Failure Resolution: Directly resolves a common cause of CI pipeline failures, ensuring smoother development workflows.
  • Use Case: When the scheduled TODO checker CI job fails, indicating that closed issues are still being referenced in code comments, this skill will identify the specific issues and reopen them with relevant context.

Quick Start

Use the fix-todo skill to resolve the latest TODO checker CI failure.

Frequently Asked Questions about fix-todo

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

FAQPage Schema
How do I automatically reopen closed GitHub issues still referenced in code TODO comments?▼

Automatically reopen closed GitHub issues flagged by TODO comments by parsing CircleCI job outputs to identify issue details and reopening them with context. The skill uses GitHub's GraphQL API to determine who closed the issue and adds a traceability comment.

Why does my CI pipeline fail when a GitHub issue referenced by a TODO comment is closed?▼

CI pipelines fail because the TODO checker flags closed issues still referenced in code comments. This occurs when code TODOs reference issues that have been resolved, causing the scheduled CI job to report a mismatch and halt the workflow.

How do I resolve TODO checker CI failures without manually finding and reopening issues?▼

Resolve TODO checker CI failures by running an automated process that identifies relevant closed issues and reopens them. It parses CircleCI outputs, identifies the last person to close the issue via GitHub's GraphQL API, and reopens it with a detailed comment.

Do I need GitHub CLI and jq installed to automate issue management for CI failures?▼

Yes, you need GitHub CLI (gh), jq, and curl installed. These dependencies are required to parse CircleCI job outputs, query GitHub's GraphQL API for issue details, and execute the automated issue reopening process.

What is the best way to add traceability when reopening issues flagged by a TODO checker?▼

Add traceability by reopening issues with a detailed comment that includes the code location and CI job traceability. The skill identifies the specific issue using CircleCI outputs and mentions the person who originally closed it via GitHub's GraphQL API.

Related Skills

Explore More Software Engineering Skills→
georgekhananaevgeorgekhananaev
27

github-cli

Wrap GitHub CLI commands with risk classification and confirmation prompts.

Community
Intermediate
nashgaonashgao
3

Create Smart TODOs

Generate contextual TODO comments in code based on project standards and issues.

Community
Intermediate
dr-codedr-code

circleci-automation

Automate CircleCI pipeline triggers, workflow listing, job inspection, and artifact retrieval via Rube MCP.

Community
Intermediate
wyhlovecppwyhlovecpp

gh-fix-ci

Extract failure details from GitHub Actions CI logs for pull requests.

Community
Intermediate