搜索「Code Review」的结果

io.github.affaan-m/ECC/santa-method

带收敛循环的多代理对抗校验。输出必须先通过两个独立评审代理才能交付。适用于交付前需由两个独立对抗评审者把关的产出。

io.github.affaan-m/ECC/orch-build-mvp

编排从设计或规格文档引导出一个可用 MVP 的过程——读取文档、规划薄的垂直切片、搭建第一个端到端切片，然后按 TDD 实现、评审并完成带门槛的提交。用于把 SDD/PRD 变成可运行的起点：当设计或规格文档需要通过规划好的垂直切片落地为可运行的 MVP 时使用。

io.github.affaan-m/ECC/springboot-verification

Spring Boot 项目的验证闭环：发布或 PR 前的构建、静态分析、带覆盖率的测试、安全扫描与差异（diff）审查。

io.github.affaan-m/ECC/django-verification

Django 项目的验证闭环：发布或 PR 前的数据库迁移、代码风格检查、带覆盖率的测试、安全扫描与部署就绪检查。

io.github.affaan-m/ECC/loop-design-check

设计以目标为导向的 Agent 循环，并排查循环常见的出错方式——原地打转烧 token、钻验证器的空子（Goodhart 效应）、把错误答案一路跑到底。包含两个动作：(1) 编写循环——先判断是否值得构建、定义机器可判定的目标、选定循环类型与脚手架；(2) 审查循环——按五种失败模式，加上可判定性、边界、兜底方案、评判者独立性，以及把判断权留在人手中这条红线逐项检查。当设计自主 Agent 循环，或已有循环但担心它跑飞、作弊或把错误答案执行到底时使用。它在机制层循环技能（autonomous-loops、continuous-agent-loop）之外补足其未覆盖的判断层。中文触发：写 loop、设计 loop、做一个 loop、检查 loop 对不对、loop 体检、loop 会不会跑飞、可判定目标、五个崩法、plan build judge。English triggers: design an agent loop, write a loop, check a loop, loop review, prevent a runaway loop, goal-oriented loop, decidable goal, plan/build/judge.

io.github.affaan-m/ECC/frontend-a11y

React 与 Next.js 的无障碍访问模式——语义化 HTML、ARIA 属性、表单标注、键盘导航、焦点管理与读屏软件支持。当构建任何交互式 UI 组件或表单时使用。

io.github.moeru-ai/airi/enforce-rules-for-typescript

Enforce AIRI's TypeScript and Vue source rules for imports, naming, comments, JSDoc, fallbacks, stateful and protocol code, and module design. Use when writing, refactoring, or reviewing TypeScript or Vue source code in the AIRI monorepo.

io.github.obra/superpowers/writing-plans

在有多步骤任务的规格或需求、但尚未动代码时使用。

io.github.tabler/tabler/backward-compat

Keep a change to `@tabler/core` backward compatible, so a patch or minor release never breaks a project that updates. Use before renaming, removing or changing the meaning of anything a user can touch — a class, a `--tblr-*` custom property, a Sass variable, mixin or function, a `data-*` attribute or option, a JS export, an event, a file under `dist/`, a default value — and whenever a changeset on `dev` looks like it needs a `major` bump. Also consult it proactively when a cleanup or refactor in `core/` deletes something, since "dead" code is often somebody's API. Covers what counts as public API, the `deprecated` files where compatibility code lives, the alias patterns, the `check:compat` gate, and what to do when a break cannot be avoided.

io.github.odoo/odoo/odoo-security

Security audit of Odoo addon code: access control (ir.access, field groups, sudo), injection (SQL, domain, eval, XSS via Markup/markup()), untrusted public methods/RPC, controller auth/CSRF, file access, deserialization, returning complex objects, getattr/setattr, timing attacks. Use when auditing an addon, or judging whether a specific construct (a sudo, raw SQL, a route, ...) is safe.

io.github.odoo/odoo/odoo-guidelines

House rules for Odoo addon code: module structure, manifest, Python/ORM, fields, controllers, XML views and data, QWeb reports, access rights and record rules, performance, tests. Use when writing or reviewing any file in an Odoo addon outside static/ (for the JavaScript, Owl templates and SCSS under static/, see odoo-web-guidelines).

io.github.mattpocock/skills/implement-spec

Implement the result of /to-spec and /to-tickets in code.

io.github.wekan/wekan/migrate-to-rspack

Use when migrating an existing Meteor app to Rspack (Meteor 3.4+), or upgrading Rspack 1 to 2 on Meteor 3.6 beta. Triggers on nested imports, mainModule entry points, server-only apps, replacing fourseven:scss / meteor/less / coffeescript / jorgenvatle:vite / zodern:melte with loaders, Svelte/TypeScript preprocessing or Lingui SWC plugin failures after upgrade, CommonJS default-import interop, module.exports in client graphs, Node built-ins in browser code, _build / build-assets / build-chunks, .meteorignore hiding handoff files, dynamic chunks under ROOT_URL, meteor.modules for CSS/HTML, resolve.symlinks or resolve.alias migration, automatic dependency updates and immutable CI/Docker builds. Use this skill when the user asks about migration compatibility or a build plugin's Rspack replacement. For new-app setup and rspack.config.js helpers, use meteor-modern-build-stack instead.

io.github.mem0ai/mem0/search

Search memories from earlier Cursor sessions in this repository. Use it when earlier work may already explain the code, error, decision, or command you need, so you can avoid repeating file reads, searches, or experiments.

io.github.getsentry/sentry/react-testing

使用 Jest 与 React Testing Library 为 Sentry 前端编写和审查 React/TypeScript 测试。在 static/ 中新增或编辑测试（*.spec.tsx）、编写组件/hook 测试、用 MockApiClient 模拟 API 响应、测试路由或网络请求，或被要求“write a frontend test”“add a React test”“test this component”“fix a flaky RTL test”时使用。

io.github.supabase/supabase/test-the-docs

在一次性的 Docker Compose 沙箱（runner 容器 + 通过 supabase start 启动的本地 Supabase 栈）里执行文档中可运行的代码片段与示例。在 Draft 之后或 Self-review 期间，被要求测试文档、对 CLI/SQL/代码样例做事实核查或为文档 PR 产出验证报告时使用。作为 review-the-docs 的 lint/build 检查的补充而非替代。

io.github.supabase/supabase/ask-the-docs

基于文档化的架构、构建流水线与 review 模式回答关于 Supabase docs 应用（apps/docs）的问题，并在提议或评审改动时套用功能设计原则（代码库复用、极简编码）。当用户问“docs 应用里 X 是怎么工作的”“Y 在哪里”“这个方案在 docs 应用里合适吗”，或在 apps/docs/ 下做非平凡改动前使用——特别是涉及 MDX 流水线、markdown 生成、内容组件、联邦文档、贡献者写作模式的场景。必要时可用 Mermaid 图回答架构问题。

io.github.remotion-dev/remotion/v5-breaking-changes

在 v4 与 v5 发布线仍共享代码期间实施或审查 Remotion 5 的破坏性变更。适用于 main 分支上必须保持 v4 行为与公共类型兼容,但切换中央 v5 开关后应启用新运行时行为、默认值或 TypeScript API 的情况。

io.github.github/awesome-copilot/api-breaking-change-detector

Cross-references C# Web API controllers/DTOs against their TypeScript/JavaScript consumers (React, Angular, Vue, Svelte, Node.js, or hand-written/auto-generated HTTP clients like Fetch, Axios, NSwag) to catch contract drift in both directions: backend changes that break client applications (renamed/removed JSON keys, new required parameters, status code shifts) and frontend code sending fields the backend no longer reads. Works directly against source code, not exported OpenAPI spec files. Use when the user asks to check for breaking API changes, verify frontend/backend contract sync, or audit a DTO/controller change against its TypeScript/JS consumers before merging. Not for generating new API code from a spec (see openapi-to-application-code) or scaffolding new endpoints (see aspnet-minimal-api-openapi).

io.github.grafana/grafana/frontend-testing-strategy

按本仓库约定为 Grafana 前端代码（React/TypeScript，任意包或功能域）编写单元与 E2E 测试。新增、补齐或审查前端测试时使用；测试仅断言“渲染成功/已定义”、AI 生成测试质量存疑、或前端测试不稳定时同样适用。涉及可视化面板与 grafana-ui 可视化组件时，另需加载 panel-testing-strategy skill。

io.github.github/awesome-copilot/macos-golden-gate-design

Design, implement, review, or refactor native macOS 27 Golden Gate interfaces in SwiftUI or AppKit. Use when a Mac app must match Apple's current macOS 27 UI kit and restrained Liquid Glass language: integrated windows, full-height sidebars, native toolbars, flat lists, tables, and forms, clear pane boundaries, accessible materials, and removal of unnecessary nested cards, framed panels, or glassmorphism. Also use for Figma macOS 27 design-to-code work and audits of interfaces that feel too boxed.

io.github.obra/superpowers/test-driven-development

在实现任何功能或修复 bug、编写实现代码之前使用。

io.github.affaan-m/ECC/tdd-workflow

在编写新功能、修复 bug 或重构代码时使用此 skill。强制推行测试驱动开发，覆盖率不低于 80%，涵盖单元、集成与 E2E 测试。

io.github.affaan-m/ECC/plan-canvas

在本地浏览器画布中打开计划与 HTML 产物，人可以在同一页面上标注元素、聊天并批准或要求修改。在展示计划供评审，或像“把这个挪一下、那个改一下”这类用指比用打字更方便的反馈时使用。