Orchestrate bug fixes — reproduce as a failing test, fix to green, gated commit
Bug-fix orchestration that reproduces the defect as a failing regression test, delegates each phase to the matching ECC agent, and gates the commit
- What
- Bug-fix orchestration that reproduces the defect as a failing regression test, delegates each phase to the matching ECC agent, and gates the commit
- Cost
- Free
- Needs
- nothing to install — the skill is a methodology your agent follows when fixing bugs; the orch-pipeline engine skill and ECC agents are needed for the full delegation (otherwise the steps still work manually)
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @affaan-m's bug-fix orchestration discipline for agents: treat every fix as a pipeline, not a patch. First move is always reproducing the defect as a new failing regression test — proving the bug exists is what separates a fix from a tweak — then fix to green, run a code review, and commit behind an explicit pre-commit gate. The workflow delegates each phase to the matching ECC agent (code-explorer when the root cause is unclear, build-error-resolver for build breaks, security-reviewer on security-sensitive paths), skips the research phase by default (a light root-cause analysis only when the cause is non-obvious), and distinguishes clearly between fixing broken behavior, changing wanted behavior, and adding missing capability. MIT-licensed. Honest caveats: it is a thin wrapper over the `orch-pipeline` engine — the engine skill and the sibling ECC agents must also be installed; like any red-green workflow it works best where the codebase already has a runnable test suite. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: nothing to install — the skill is a methodology your agent follows when fixing bugs; the orch-pipeline engine skill and ECC agents are needed for the full delegation (otherwise the steps still work manually) Install "Orchestrate bug fixes — reproduce as a failing test, fix to green, gated commit" for me. It gives my agent @affaan-m's bug-fix orchestration: first reproduce the defect as a new failing regression test, fix until green, run a review, and commit behind an explicit pre-commit gate — delegating each phase to the matching ECC agent (code-explorer, build-error-resolver, security-reviewer) and skipping research unless the root cause is unclear. MIT-licensed. Repository: https://github.com/affaan-m/ecc/blob/main/skills/orch-fix-defect/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "orch-fix-defect". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. nothing — it is a methodology; tell the agent to follow it the next time something is broken). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.