用于审查或改进前端无障碍、语义结构、键盘支持、焦点管理、ARIA 标签、屏幕阅读器行为、WCAG 2.2 问题、触控无障碍或辅助技术回归；中文触发词包括 无障碍、accessibility、a11y、WCAG、屏幕阅读器。
The English summary is being prepared. Showing the original description.
bovinphang/frontend-craft22Updated Sep 26, 2026
FreePublished on GitHub
fec-validation-fix
用于运行现有项目验证命令并修复代码变更后的失败，包括 lint、type-check、单元/集成测试、build、CI 或本地脚本失败。不要用于设计或编写新的组件/E2E 测试；中文触发词包括 验证、检查失败、修复失败、CI 失败。
The English summary is being prepared. Showing the original description.
See how to installFiles included (2)
- SKILL.md2.1 KB
- references/report-template.md1.0 KB
SKILL.md (original)
Review the instructions the agent will receive before you install.
验证并修复
用途
自动化执行已有验证命令，分析失败原因并安全修复，确保质量门禁达标。
流程
- 从 package.json 或仓库文档中识别可用命令。
- 优先按以下顺序执行：
- lint
- type-check
- unit/integration tests
- build
- 仔细阅读失败输出。
- 将错误按文件、错误类型和依赖关系分组，优先处理阻塞后续诊断的根因。
- 一次只修复一类问题，并显示或记录关键错误上下文。
- 每次关键修复后重新执行受影响命令，确认错误是否减少。
- 如果同一错误连续三次修复仍失败，停止扩大改动并报告阻塞。
- 最后按“预期输出”总结执行结果、修复内容和剩余风险。
失败分诊
- 先修最早出现且会级联的错误，例如缺失类型、导入失败、配置解析失败。
- 区分真实产品 bug、测试环境问题、快照漂移、依赖版本变化和 flaky。
- 对 CI 专属失败记录 Node 版本、包管理器、环境变量、路径大小写和工作目录差异。
- 修复测试时优先修产品代码或测试等待方式，不用删除断言掩盖真实回归。
约束
- 不要盲目关闭规则来消除报错
- 除非有明确理由，不要为了通过检查而降低类型安全
- 不要因为附近测试失败就顺手重写无关模块
- 不要一次性修改多个无关根因
- 不要删除失败测试来让验证通过
- 不要只运行失败命令的片段就声称整体验证通过
详细参考
撰写验证修复报告时，加载 references/report-template.md。
预期输出
- lint / type-check / test / build 等验证命令全部通过
- 失败项已修复或给出明确原因和后续行动
- 修复报告保存为
reports/validation-fix-YYYY-MM-DD-HHmmss.md
Reviews
No reviews yet. Tell others what you thought.
Comments
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
More skills from this repository
Use when reviewing or improving frontend accessibility, semantic structure, keyboard support, focus management, ARIA labels, screen reader behavior, WCAG 2.2 issues, touch accessibility, or assistive-technology regressions; Chinese triggers include accessibility, accessibility, a11y, WCAG, screen reader.
The English summary is being prepared. Showing the original description.
bovinphang/frontend-craft22Updated Sep 26, 2026
fec-alchemy
FreeUse when absorbing ideas, capabilities, workflows, architecture, quality systems, ecosystem extensions, or engineering practices from any reference system into the current project through original, project-native redesign rather than copying.
The English summary is being prepared. Showing the original description.
bovinphang/frontend-craft22Updated Sep 26, 2026
fec-alchemy
Free用于从参考系统中吸收想法、能力、工作流、架构、质量体系、生态扩展或工程实践，并通过原创的项目内重设计转化为当前项目能力，而不是复制原实现。
The English summary is being prepared. Showing the original description.
bovinphang/frontend-craft22Updated Sep 26, 2026
用于设计、实现或审查前后端 API 集成、类型化 API client、REST/tRPC/OpenAPI 客户端选型、认证刷新、API 错误映射、上传流程、SSE/WebSocket/轮询选择、CORS 相关前端行为或跨边界 loading/error 状态。不要用于纯后端服务架构或仅 TanStack Query 缓存策略；中文触发词包括 API 集成、前后端联调、typed API client、接口错误处理、SSE、WebSocket。
The English summary is being prepared. Showing the original description.
bovinphang/frontend-craft22Updated Sep 26, 2026
Use when designing, implementing, or reviewing frontend-to-backend API integration, typed API clients, REST/tRPC/OpenAPI client choices, auth refresh, API error mapping, upload flows, SSE/WebSocket/polling choices, CORS-facing frontend behavior, or cross-boundary loading/error states. Do not use for backend-only service architecture or TanStack Query cache policy alone; Chinese triggers include API integration, front-end and back-end joint debugging, typed API client, Interface error handling, SSE, WebSocket.
The English summary is being prepared. Showing the original description.
bovinphang/frontend-craft22Updated Sep 26, 2026