frontend-error-diagnose
Skill1 starsChanged 47 days agoGPL-3.0View on GitHub
前端报错诊断的标准工作流：先用浏览器 MCP 复现报错，采集 console 报错、失败请求与 JS 调用栈等证据，定位根因后给出可执行的修复方案。当用户给出前端报错（APM/监控平台上报的 JS 报错、浏览器控制台报错、页面白屏、接口 4xx/5xx、CORS、资源加载失败等）并要求"分析是什么问题导致的报错""先复现再分析""给出解决方案"时使用——不凭报错文案猜结论、先复现再定位；默认只诊断不改代码；无法复现时按三档降级并说明档位，不静默跳过。即使未明确说"用 skill"，只要涉及前端报错定位就应使用。需要直接改代码修复用 bug-fix；报错指向后端、需拉日志定位根因用 log-diagnose；需核对业务数据状态用 db-query（生产只读）。
In this repository30 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- app-packagingSkill
- bug-fixSkill
- check-rule-extractSkill
- code-optimizeSkill
- code-reviewSkill
- comment-supplementSkill
- commit-createSkill
- db-querySkill
- doc-syncSkill
- feature-devSkill
- git-clean-branchesSkill
- git-history-rewriteSkill
- git-rollbackSkill
- git-worktreeSkill
- i18n-transformSkill
- log-diagnoseSkill
- module-batchSkill
- mr-createSkill
- nas-disk-diagnosticSkill
- opencode-batchSkill
- project-explainSkill
- refactorSkill
- repo-initSkill
- session-summarySkill
- skill-routerSkill
- spec-routeSkill
- task-commanderSkill
- unit-testSkill
The file
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.