Communitygithub.com

orch-fix-defect

Orquesta la corrección de un fallo: reprodúcelo como una prueba de regresión fallida, arréglalo hasta que pase, revísalo y confírmalo antes de integrar, delegando cada fase al agente ECC adecuado. Úsalo cuando el comportamiento existente está roto o es incorrecto.

¿Qué es orch-fix-defect?

Este skill, `orch-fix-defect`, está diseñado para corregir fallos en software de forma estructurada y controlada, ideal para entornos de desarrollo con múltiples agentes especializados (tipo ECC). Su valor principal es garantizar que, antes de aplicar cualquier cambio, se demuestre la existencia del error mediante una prueba de regresión que falle inicialmente. Soporta plataformas de agentes como Claude Code, Cursor, Codex y herramientas similares que permitan orquestar pipelines de tareas. El skill funciona como un wrapper fino sobre el motor compartido `orch-pipeline`, configurando una secuencia de fases: si la causa raíz no es obvia, se explora con `code-explorer`; luego se escribe la prueba fallida (fase 4), se corrige el código hasta que la prueba pase (fase 5), se realiza una revisión de código (fase 6) y se detiene en dos puntos de control (Gate 1 y Gate 2) para validación humana. Está pensado para fallos concretos (errores, crashes, regresiones) no para cambios de funcionalidad o nuevas características.

Compatible con✓Claude Code~Codex CLI~Cursor
npx skills add https://github.com/affaan-m/ECC/tree/main/skills/orch-fix-defect

Preguntar en tu IA favorita

Abre un nuevo chat con esta habilidad de agente ya precargada.

Documentación

¿Qué hace orch-fix-defect?

Actor · acción · objetivo: orch · fix · defect. Wrapper fino sobre el motor compartido en orch-pipeline.

Cuándo usarlo

  • Algo está roto: salida incorrecta, un error, un crash, una regresión.
  • Distinguir de skills similares:
    • el comportamiento es correcto pero se quiere diferente → orch-change-feature.
    • la capacidad no existe aún → orch-add-feature.

Ajustes de operación

  • Tamaño mínimo por defecto: pequeño (a menudo trivial).
  • Máscara de fase: 0 → (luz 2 solo si la causa raíz no es obvia o estándar+) → 4 → 5 → 6. Normalmente se omite la investigación (1).
  • Primer movimiento (fase 4): reproducir el fallo como una nueva prueba que falla (prueba de regresión), luego corregir hasta que pase. Demostrar primero que el fallo existe es lo que diferencia una corrección de un ajuste.

Cómo funciona

  1. Ejecuta el motor orch-pipeline con los ajustes anteriores.
  2. Si la causa raíz no está clara, delimítala con code-explorer antes de la prueba roja; escala los errores de compilación a build-error-resolver / /build-fix.
  3. Detente en el Gate 1 (solo si se generó un plan) y en el Gate 2 (pre-commit).
  4. Añade security-reviewer si el fallo se encuentra en una ruta sensible a seguridad.

Ejemplo

orch-fix-defect: el poller falla al recibir una respuesta NWS vacía
→ escribir prueba fallida que reproduzca el fallo → corregir hasta que pase
→ revisión de código → commit  [GATE 2: confirmar]   (commit: fix:)

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

accessibility

Design, implement, and audit inclusive digital products using WCAG 2.2 Level AA. Use when building or auditing UI that must meet WCAG 2.2 Level AA, or when reviewing a change for keyboard, contrast, or screen-reader support.

affaan-m/content-engine

Create platform-native content systems for X, LinkedIn, TikTok, YouTube, newsletters, and repurposed multi-platform campaigns. Use when the user wants social posts, threads, scripts, content calendars, or one source asset adapted cleanly across platforms.

affaan-m/ECC

Multi-platform content distribution across X, LinkedIn, Threads, and Bluesky. Adapts content per platform using content-engine patterns. Never posts identical content cross-platform. Use when the user wants to distribute content across social platforms.

affaan-m/fal-ai-media

Unified media generation via fal.ai MCP — image, video, and audio. Covers text-to-image (Nano Banana), text/image-to-video (Seedance, Kling, Veo 3), text-to-speech (CSM-1B), and video-to-audio (ThinkSound). Use when the user wants to generate images, videos, or audio with AI.

affaan-m/manim-video

日本語翻訳:このファイルは manim-video 用の日本語翻訳が必要です

affaan-m/remotion-video-creation

Remotion のベストプラクティス - React で動画を作成する。3D、アニメーション、音声、字幕、チャート、トランジションなどをカバーするドメイン固有の29のルール。

affaan-m/video-editing

AI-assisted video editing workflows for cutting, structuring, and augmenting real footage. Covers the full pipeline from raw capture through FFmpeg, Remotion, ElevenLabs, fal.ai, and final polish in Descript or CapCut. Use when the user wants to edit video, cut footage, create vlogs, or build video content.

agent-architecture-audit

Full-stack diagnostic for agent and LLM applications. Audits the 12-layer agent stack for wrapper regression, memory pollution, tool discipline failures, hidden repair loops, and rendering corruption. Produces severity-ranked findings with code-first fixes. Essential for developers building agent applications, autonomous loops, or any LLM-powered feature. Use when an agent or LLM feature misbehaves and the failing layer is unknown, or before shipping an agent stack.

agent-eval

Head-to-head comparison of coding agents (Claude Code, Aider, Codex, etc.) on custom tasks with pass rate, cost, time, and consistency metrics. Use when choosing between coding agents, or when a change to an agent setup needs measured pass rate, cost, and time rather than an impression.

agent-harness-construction

Design and optimize AI agent action spaces, tool definitions, and observation formatting for higher completion rates. Use when defining or revising an agent

agentic-engineering

Operate as an agentic engineer using eval-first execution, decomposition, and cost-aware model routing. Use when planning or executing engineering work that agents will carry out end to end.

agentic-os

Build persistent multi-agent operating systems on Claude Code. Covers kernel architecture, specialist agents, slash commands, file-based memory, scheduled automation, and state management without external databases. Use when building a persistent multi-agent system on Claude Code with its own memory, commands, and scheduling.

agent-introspection-debugging

Structured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports. Use when an agent run fails and you need a reproducible diagnosis instead of a retry.

agent-payment-x402

Add x402 payment execution to AI agents with per-task budgets, spending controls, and non-custodial wallets. Supports Base through agentwallet-sdk and X Layer through OKX Payments / OKX Agent Payments Protocol. Use when an agent must pay for something itself and needs per-task budgets, spending controls, and a non-custodial wallet.

agent-self-evaluation

Use after completing any non-trivial task. The agent self-rates its output on 5 axes — accuracy, completeness, clarity, actionability, conciseness — with concrete evidence per criterion. Produces a structured 1-5 scorecard with specific improvement suggestions.

agent-sort

Build an evidence-backed ECC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when ECC should be trimmed to what a project actually needs instead of loading the full bundle.

ai-first-engineering

Engineering operating model for teams where AI agents generate a large share of implementation output. Use when setting team process, review gates, or ownership rules for a codebase largely written by agents.

ai-regression-testing

Regression testing strategies for AI-assisted development. Sandbox-mode API testing without database dependencies, automated bug-check workflows, and patterns to catch AI blind spots where the same model writes and reviews code. Use when adding regression coverage to AI-assisted code, or when the same model both wrote and reviewed a change.

android-clean-architecture

Clean Architecture patterns for Android and Kotlin Multiplatform projects — module structure, dependency rules, UseCases, Repositories, and data layer patterns. Use when structuring modules, layers, or data flow in an Android or KMP project.

angular-developer

Generates Angular code and provides architectural guidance. Trigger when creating projects, components, or services, or for best practices on reactivity (signals, linkedSignal, resource), forms, dependency injection, routing, SSR, accessibility (ARIA), animations, styling (component styles, Tailwind CSS), testing, or CLI tooling.

Skills relacionados