agentsclimarketplace

Fec validation fix

Skill bovinphang/frontend-craft/localized/zh-CN/skills/fec-validation-fix

frontend-craft is a universal frontend plugin that brings the same opinionated engineering standards to all 15 AI coding assistants.

Install
npx -y skills add bovinphang/frontend-craft --skill fec-validation-fix

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 19 stars19 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

用于运行现有项目验证命令并修复代码变更后的失败，包括 lint、type-check、单元/集成测试、build、CI 或本地脚本失败。不要用于设计或编写新的组件/E2E 测试；中文触发词包括 验证、检查失败、修复失败、CI 失败。

SKILL.md

2.1 KB, 628 tokens by cl100k_base, as published. Nobody here has run it

验证并修复

用途

自动化执行已有验证命令，分析失败原因并安全修复，确保质量门禁达标。

流程

  1. 从 package.json 或仓库文档中识别可用命令。
  2. 优先按以下顺序执行：
    • lint
    • type-check
    • unit/integration tests
    • build
  3. 仔细阅读失败输出。
  4. 将错误按文件、错误类型和依赖关系分组，优先处理阻塞后续诊断的根因。
  5. 一次只修复一类问题，并显示或记录关键错误上下文。
  6. 每次关键修复后重新执行受影响命令，确认错误是否减少。
  7. 如果同一错误连续三次修复仍失败，停止扩大改动并报告阻塞。
  8. 最后按“预期输出”总结执行结果、修复内容和剩余风险。

失败分诊

  • 先修最早出现且会级联的错误，例如缺失类型、导入失败、配置解析失败。
  • 区分真实产品 bug、测试环境问题、快照漂移、依赖版本变化和 flaky。
  • 对 CI 专属失败记录 Node 版本、包管理器、环境变量、路径大小写和工作目录差异。
  • 修复测试时优先修产品代码或测试等待方式，不用删除断言掩盖真实回归。

约束

  • 不要盲目关闭规则来消除报错
  • 除非有明确理由，不要为了通过检查而降低类型安全
  • 不要因为附近测试失败就顺手重写无关模块
  • 不要一次性修改多个无关根因
  • 不要删除失败测试来让验证通过
  • 不要只运行失败命令的片段就声称整体验证通过

详细参考

撰写验证修复报告时，加载 references/report-template.md。

预期输出

  • lint / type-check / test / build 等验证命令全部通过
  • 失败项已修复或给出明确原因和后续行动
  • 修复报告保存为 reports/validation-fix-YYYY-MM-DD-HHmmss.md

Gives 0 of the 12 instructions most quality gates skills give in 628 tokens

Counted across 1,195 of the 2,094 authors here whose files we hold, read 2026-08-07

  • read the output and check the exit codein 54 of 1195, across 14 files
  • verify requirements using a line-by-line checklistin 53 of 1195, across 12 files
  • identify the verification command proving the claimin 51 of 1195, across 12 files
  • run the full verification commandin 50 of 1195, across 11 files
  • verify output confirms the claimin 49 of 1195, across 12 files
  • check version control diff after agent delegationin 46 of 1195, across 6 files
  • state claim with evidencein 44 of 1195, across 4 files
  • run the test suitein 33 of 1195, across 26 files
  • keep state in memory by defaultin 27 of 1195, across 6 files
  • make prototype runnable with one commandin 26 of 1195, across 5 files
  • produce a verification reportin 25 of 1195, across 14 files
  • detect the package manager from lockfilesin 24 of 1195, across 5 files

Said here and by no other author read

  • identify available commands from project configuration
  • fix root causes blocking further diagnosis first
  • fix one problem class at a time
  • rerun affected commands after each key fix
  • distinguish real bugs from environment or flaky issues
  • record CI-specific environment differences

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.