CJ_goal_todo_fix

Automates resolution of TODOs in a TODOS.md file by creating Pull Requests with implementation, QA, and deployment steps.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/jcl2018/claude-skills-templates --skill cj-goal-todo-fix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: CJ_goal_todo_fix
Source: https://github.com/jcl2018/claude-skills-templates/tree/main/skills/CJ_goal_todo_fix
Command: npx skills add https://github.com/jcl2018/claude-skills-templates --skill cj-goal-todo-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires CJ_implement_from_spec, CJ_qa_work_item, ship, land_and_deploy, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the resolution of TODOs in a TODOS.md file by converting them into Pull Requests, streamlining the workflow and saving time.

Core Features & Use Cases

  • TODO to PR Conversion: Converts TODO entries in a TODOS.md file into Pull Requests with automated steps.
  • Customizable Workflows: Offers customizable steps, including code implementation, QA, and deployment.
  • Integration with Other Skills: Integrates with other skills for tasks like implementation, QA, and deployment.
  • Use Case: Imagine you have a TODO in your TODOS.md file to implement a new feature. Use this Skill to automatically create a PR with the feature implementation, run QA, and deploy the change.

Quick Start

Use the CJ_goal_todo_fix skill with the command: /CJ_goal_todo_fix

Frequently Asked Questions about CJ_goal_todo_fix

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

FAQPage Schema
How do I automate creating a pull request from a TODO entry in a markdown file?

You can automate TODO to PR conversion by using this Skill to read TODOS.md entries and execute code implementation, QA, and deployment steps automatically. It directly transforms markdown TODOs into merged code changes without manual intervention.

What is the workflow for converting TODOS.md entries into GitHub pull requests?

The workflow for converting TODOS.md entries into GitHub pull requests involves automated code implementation, followed by QA, and concluding with deployment. It integrates with specialized skills to handle each phase sequentially, ensuring the TODO is fully resolved before the PR is finalized.

Do I need other skills to automate code implementation and QA for my TODOs?

Yes, you need other skills to automate code implementation and QA for your TODOs. This Skill requires integration with dependencies like CJ_implement_from_spec for writing code, CJ_qa_work_item for testing, and ship for deployment to function properly.

Can I customize the code review and deployment steps when resolving TODOs?

Yes, you can customize the code review and deployment steps when resolving TODOs. The Skill offers customizable workflows, allowing you to configure the automated implementation, QA, and deployment actions applied to each pull request generated from your TODOS.md file.

Does this TODO automation tool support deployment after the PR is created?

Yes, this TODO automation tool supports deployment after the PR is created. It integrates with the ship and land_and_deploy skills to automatically execute deployment steps once the code implementation and QA phases are successfully completed.