CJ_goal_task

Convert small ad-hoc tasks into pull requests via bash scripting.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of converting small, ad-hoc tasks into reviewable pull requests, eliminating the need for design or investigation.

Core Features & Use Cases

  • Automated Task to PR Conversion: Take a plain text task description and convert it into a pull request with minimal steps.
  • Complexity Gate: Prevents tasks that require design or investigation from being converted.
  • Silent Build and PR Creation: The process runs silently and stops at the PR for human review.
  • Use Case: If you have a small task like 'refine a doc', 'add a file', or 'clean up files', use this Skill to generate a PR without the need for an office hours or design document.

Quick Start

Use the /CJ_goal_task "refine this document" command to convert your task into a PR.

Frequently Asked Questions about CJ_goal_task

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

FAQPage Schema
How do I convert ad-hoc tasks into pull requests automatically?

To convert ad-hoc tasks into pull requests, use a task automation skill that takes plain text task descriptions and generates a PR. This requires a git repository and a script environment to process the task silently and stop for human review.

What is the best way to automate PR creation for small administrative tasks?

Automating PR creation for small administrative tasks is best handled by converting plain text descriptions directly into reviewable PRs without requiring design documents. This approach suits low-complexity, task-driven operations like refining docs or cleaning up files.

Do I need a design document to generate a PR for simple file cleanups?

No, you do not need a design document to generate a PR for simple file cleanups. The complexity gate prevents tasks requiring design or investigation from being converted, allowing low-complexity administrative workflows to proceed directly to PR creation.

Can I use bash scripting to automate task to PR conversion in a git repository?

Yes, you can use bash scripting to automate task to PR conversion in a git repository. The process relies on bash scripting and automated tool execution to handle low-complexity operations and produce reviewable pull requests silently.

When should I not use automated PR creation for task automation?

You should not use automated PR creation for task automation when your task requires design or investigation. The complexity gate blocks these higher-complexity tasks, ensuring only low-complexity, task-driven operations are processed into pull requests.