AGENT SKILL

orch-fix-defect

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.

License 许可
MIT
最近更新
2026-11-05
Stars
★ 2
Forks
1

01 前言 Front Matter

name
orch-fix-defect
metadata
{ "origin": "ECC" }
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.

03 SKILL.md 正文

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:)

04 同仓库更多 Skills

lytong760-cell
lytong760-cell/compiler_ko

x-api

X/Twitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.

★ 2
lytong760-cell
lytong760-cell/compiler_ko

writing-for-agents

Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.

★ 2
lytong760-cell
lytong760-cell/compiler_ko

workspace-surface-audit

Audit the active repo, MCP servers, plugins, connectors, env surfaces, and harness setup, then recommend the highest-value ECC-native skills, hooks, agents, and operator workflows. Use when the user wants help setting up Claude Code or understanding what capabilities are actually available in their environment.

★ 2
lytong760-cell
lytong760-cell/compiler_ko

wizard

Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.

★ 2
lytong760-cell
lytong760-cell/compiler_ko

windows-desktop-e2e

E2E testing for Windows native desktop apps (WPF, WinForms, Win32/MFC, Qt) using pywinauto and Windows UI Automation. Use when writing E2E tests for a Windows native desktop app with pywinauto or UI Automation.

★ 2
lytong760-cell
lytong760-cell/compiler_ko

wayfinder

Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.

★ 2