Skip to content
cccskills
FreePublished on GitHubEnglish overview

orch-fix-defect

Coordinate bug fixes by assigning each phase to an appropriate ECC agent. First reproduce the problem with a failing test, then fix it, review the changes, and request approval before committing.

OriginalShow the original description

Orchestrate fixing a bug — reproduce it as a failing regression test, fix to green, review, and gated commit — by delegating each phase to the matching ECC agent. Use when existing behavior is broken or wrong.

AI rating90/ 100See how to install

Good for

  • Fixing crashes or incorrect output
  • Adding a test to catch a recurring bug
  • Investigating a bug with an unclear cause
  • Taking a fix through review and commit approval

Overview

What it does

Fixes broken existing features, including incorrect output, errors, and crashes, from test reproduction through implementation, review, and commit. It assigns each phase to the appropriate ECC agent and coordinates the work through the shared orch-pipeline engine. A new failing test first demonstrates the bug. The implementation is then fixed until that test passes, confirming both the original problem and the result of the fix.

When it helps

Use it when something that previously worked breaks or produces unexpected results. When the cause is unclear, code-explorer investigates it. Build problems go to a dedicated agent, and changes in security-sensitive areas receive an additional review. It also helps create tests that detect a recurrence and organize review before committing.

Example requests

  • “Fix the poller crash on an empty NWS response, starting with a test that reproduces it.”
  • “Investigate this bug, implement a fix, and take it through code review.”

Notes

This skill requires orch-pipeline and the ECC agents responsible for each phase. If a plan is created, work pauses for approval at the plan review stage. Approval is always required before committing. Changes to correct existing behavior and additions of new features belong to other skills.

This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.

Objective evaluation

AI rated this skill on four points using only the contents of its SKILL.md. Stars and popularity are not taken into account.

Clear instructionsIs it clear when to use it and what it does?
AGoodIt identifies incorrect output and crashes as targets and explicitly distinguishes bug fixes from behavior changes and new features.
Concrete stepsAre steps, inputs, outputs, and examples spelled out?
AGoodIt specifies and illustrates the sequence of failing test, fix, review, and approval-gated commit.
SafetyAre sending data, deleting files, and running commands disclosed?
AGoodIt requires approval gates for generated plans and commits, plus extra review for security-sensitive defects.
Easy setupDoes it need few tools or API keys, and are they documented?
BPartly lackingIt depends on orch-pipeline and multiple ECC agents but provides no installation instructions.

The total counts each point as A = 25, B = 15, C = 5. Rated by AI (OpenAI Codex) as of Oct 19, 2026. Treat it as a guide and read the original before installing.

Disagree? Request a re-evaluation

Tell us which point is wrong and why. No login needed. We will check it against the SKILL.md, redo the evaluation, and show the result here.

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

Files included (1)

  • SKILL.md1.6 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

orch-fix-defect

Actor · action · target: orch · fix · defect. Thin wrapper over the shared engine in orch-pipeline.

When to Use

  • Something is broken: wrong output, an error, a crash, a regression.
  • Distinguish from siblings:
    • behavior is correct but you want it different → orch-change-feature.
    • the capability does not exist yet → orch-add-feature.

Operation settings

  • Default size floor: small (often trivial).
  • Phase mask: 0 → (light 2 only if root cause is non-obvious or standard+) → 4 → 5 → 6. Research (1) is usually skipped.
  • First move (phase 4): reproduce the bug as a new failing test (regression test), then fix until it goes green. Proving the bug exists first is what separates a fix from a tweak.

How It Works

  1. Run the orch-pipeline engine with the settings above.
  2. If the root cause is unclear, scope it with code-explorer before the red test; escalate build breaks to build-error-resolver / /build-fix.
  3. Stop at Gate 1 (only if a plan was produced) and Gate 2 (pre-commit).
  4. Add security-reviewer if the defect sits in a security-sensitive path.

Example

orch-fix-defect: poller crashes on empty NWS response
→ write failing test reproducing the crash → fix to green
→ code-review → commit  [GATE 2: confirm]   (commit: fix:)

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

accessibility

FreeSummaryAI rating 100

Design and audit interfaces for Web, iOS, and Android using WCAG 2.2 accessibility guidance. Check screen-reader labels, keyboard navigation, contrast, and control sizes to identify barriers and guide implementation for people using assistive technology.

  • Adding descriptive labels to icon-only buttons
  • Reviewing keyboard navigation and modal focus
  • Checking contrast and control sizes
affaan-m/ECC283.7KUpdated Oct 16, 2026

agent-architecture-audit

FreeSummaryAI rating 80

Investigate unreliable AI agents across 12 layers, including instructions, memory, tool execution, and display. Use code and logs to trace failures, rank findings by severity, and produce an ordered repair plan that prioritizes code changes.

  • Investigating failures that appear only inside an agent application
  • Tracing old conversation content leaking into new sessions
  • Checking skipped or falsely claimed tool execution
affaan-m/ECC283.7KUpdated Oct 16, 2026

agent-eval

FreeSummaryAI rating 80

Compare coding agents on tasks from your own codebase. Define success checks, run agents in separate Git working directories, and report pass rates, available API costs, completion time, and consistency across repeated trials.

  • Comparing coding agents on real development tasks
  • Evaluating a new tool or model before adoption
  • Checking performance after agent updates
affaan-m/ECC283.7KUpdated Oct 16, 2026

agent-harness-construction

FreeSummaryAI rating 100

Design and refine an AI agent’s available actions, tool inputs, and result formats. Define recovery steps for errors, manage the information kept in context, and evaluate changes through completion rates, retries, and cost per successful task.

  • Define an AI agent’s tool set and input formats
  • Make tool results and next steps easier to interpret
  • Specify safe retries and stopping conditions
affaan-m/ECC283.7KUpdated Oct 16, 2026

agent-introspection-debugging

FreeSummaryAI rating 100

Diagnose failed AI agent runs by capturing errors, checking likely causes, and choosing small, reversible recovery actions. The workflow produces a structured report of the failure, recovery steps, and evidence, helping explain repeated retries or stalled progress.

  • Diagnosing repeated tool calls with no progress
  • Investigating quality loss as context grows
  • Checking file paths and environment mismatches
affaan-m/ECC283.7KUpdated Oct 16, 2026

agent-introspection-debugging

FreeSummaryAI rating 100

Diagnose AI agent runs that fail repeatedly, loop through tools, or lose track of the task. Capture errors and environment details, test a focused recovery action, and produce a report explaining the evidence and outcome.

  • Diagnosing repeated failures in an agent run
  • Investigating loops through the same tool calls
  • Reviewing output degradation as context grows
affaan-m/ECC283.7KUpdated Oct 5, 2026

See all skills by affaan-m

Report a problem with this skill