Communitygithub.com

缺陷修复编排

编排缺陷修复流程:将缺陷重现为回归测试、修复至测试通过、审查并提交,委托各阶段到对应的ECC智能体。当现有行为出现错误或异常时使用。

缺陷修复编排 是什么?

一个用于编排缺陷修复工作流的AI智能体技能,能自动将bug报告分解为可执行的修复流水线。它本质上是对 `orch-pipeline` 共享引擎的薄包装,通过定义明确的阶段屏蔽(phase mask)来控制执行的深度和顺序。该技能支持Cursor、Codex、Claude Code等主流AI开发平台。与 `orch-change-feature`(行为变更)和 `orch-add-feature`(新增功能)不同,它专注于修复**已存在但错误**的行为。其核心工作流是:先创建一个失败的回归测试来证明bug存在(阶段4),然后编写修复代码直至测试通过,并集成代码审查和门控提交(Gate 2)。对于根本原因不明确的情况,它还能自动调用 `code-explorer` 进行范围界定,并在构建失败时委托 `build-error-resolver` 处理。默认问题规模为“小”(通常较简单),安全敏感路径会自动附加 `security-reviewer` 审查,确保修复质量。

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

在你喜欢的 AI 中提问

打开一个已预加载此 Agent Skill 的新对话。

文档

缺陷修复编排 是做什么的?

行为体 · 动作 · 目标:orch · fix · defect。对共享引擎 orch-pipeline 的薄包装。

使用时机

  • 某些东西 坏了:输出错误、报错、崩溃、回归。
  • 与同类技能区分:
    • 行为正确但希望变更 → orch-change-feature。
    • 该能力尚不存在 → orch-add-feature。

操作设置

  • 默认规模下限: 小(通常较简单)。
  • 阶段屏蔽: 0 →(仅当根本原因不明显或标准及以上时才启用轻量阶段2)→ 4 → 5 → 6。研究阶段(1)通常跳过。
  • 第一步(阶段4): 将 bug 重现为一个 新的失败 测试(回归测试),然后修复直到测试通过。先证明 bug 存在,这是将修复与微调区分开的关键。

工作原理

  1. 使用上述设置运行 orch-pipeline 引擎。
  2. 如果根本原因不明确,在红色测试之前先用 code-explorer 进行范围界定;构建失败则升级给 build-error-resolver / /build-fix 处理。
  3. 在 门控1(仅在生成计划后)和 门控2(预提交)停止。
  4. 如果缺陷位于安全敏感路径中,则附加 security-reviewer。

示例

缺陷修复编排:轮询器在空NWS响应时崩溃
→ 编写失败的测试重现崩溃 → 修复直到测试通过
→ 代码审查 → 提交  [门控2:确认]  (提交信息: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.

相关技能