CJ_goal_defect

Orchestrate defect resolution from bug description to fix deployment.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, bash, jq, scripts/cj-goal-common.sh, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process from a bug description to a shipped fix, reducing manual effort and improving defect resolution efficiency.

Core Features & Use Cases

  • Bug Description to Fix: Automates the creation of a draft, investigation, root cause analysis, and final fix deployment.
  • Root Cause Analysis: Utilizes an agent subagent to perform root cause analysis with iron-law enforcement.
  • Work Item Promotion: Promotes the draft to a canonical defect directory with a minted defect ID.
  • QA and Deployment: Executes QA checks and deploys the fix to the production environment.
  • Use Case: If you have a bug report with no pre-existing defect directory, use this Skill to automatically orchestrate the bug investigation, fix, and deployment.

Quick Start

Run the command /CJ_goal_defect "Your bug description here" to start the defect resolution process.

Frequently Asked Questions about CJ_goal_defect

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

FAQPage Schema
How do I automate bug resolution from description to code deployment?

Automating bug resolution from description to code deployment involves orchestrating a workflow that handles bug investigation, root cause analysis, QA validation, and final fix deployment within a git repository environment.

What's the best way to streamline root cause analysis for CI/CD bug tracking?

Streamlining root cause analysis for CI/CD bug tracking is best achieved by using an agent subagent to perform the analysis with iron-law enforcement, ensuring structured defect investigation before promoting a draft to a canonical defect directory.

Do I need a git repository to orchestrate defect resolution and bug tracking?

Yes, you need a git repository to orchestrate defect resolution. The process also requires bash and jq for scripting and markdown processing to successfully manage bug investigation and code deployment.

Can I promote a bug draft to a canonical defect directory with a minted defect ID?

Yes, you can promote a bug draft to a canonical defect directory. The orchestration process automatically mints a unique defect ID for the work item during the promotion phase.

How does sentinel-wrapped JSON work for subagent communication during defect resolution?

Sentinel-wrapped JSON works for subagent communication by structuring the data exchange between the bug investigation, root cause analysis, and QA validation agents, ensuring reliable orchestration throughout the defect resolution workflow.

When should I not use an automated orchestration process for defect resolution?

You should not use an automated orchestration process for defect resolution when a pre-existing defect directory already exists for the bug report, as this workflow is designed specifically for new bug descriptions without prior canonical tracking.