← Search

Orchestrate bug fixes — reproduce as a failing test, fix to green, gated commit
Developer tools 🧪 Install ran in our test sandbox · Nov 11, 2026 📌 Pinned version: commit 4eb71d9
Install test only, on the date shown. This does not guarantee the code is safe.
⚙ Needs: nothing to install…

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

At a glance
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.

Version:

Quick answer

Orchestrate bug fixes — reproduce as a failing test, fix to green, gated commit is a free Muse skill that treats every fix as a pipeline, not a patch, always reproducing the defect first as a new failing regression test, then fixing to green, running a code review, and committing behind an explicit pre-commit gate.

⌁

Install

Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 4eb71d9

Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. 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://raw.githubusercontent.com/affaan-m/ecc/4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2/skills/orch-fix-defect/SKILL.md Pinned version: install the code at commit 4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 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.

🔒 Security, provenance and what this touches
🧭 What this touches
Based on the install prompt we scanned, this skill does not run commands, make third-party network calls, install packages, write files, or ask for API keys.
Install prompt analysis · 2026-10-13
🔒 Security and provenance
📌 Pinned version: commit 4eb71d9 · 2026-10-13
🧪 Install ran in our test sandbox · Nov 11, 2026
👁 Observed during the install test · Nov 11, 2026 : no network contact
🔎 Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a skill before installing →

✓

Verification certificate

Dated facts about what was checked for this listing, and how. This is not a safety certification.

Pinned version
4eb71d9 · 2026-10-13
Sandbox install test
Install ran in our test sandbox · Nov 11, 2026
Creator identity
Not verified
Fingerprint watch
Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Install prompt analysis
2026-10-13 : No commands, network calls, packages, file writes or API keys detected.

Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify

?

Questions

How do I install a skill?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill 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 skill before installing it.