log-diagnose
Skill1 starsChanged 48 days agoGPL-3.0View on GitHub
日志自动诊断 — 按 trace_id（或 --kw 关键词/业务单号）+ 时间窗从 Kibana（多环境，--env 切换）拉取日志，定位错误根因；需要核对业务数据状态时用 db-query skill 查库佐证（生产只读）；判定为 BUG（含查询超时引发报错）时产出修复任务 MD 与独立事故报告 MD 两份文档。当用户给出 trace_id / 日志片段 / 业务单号（单据号、订单号等）要求排查线上问题、定位错误根因、判断是否 bug 时使用，即使未明确说"用 skill"。边界：需要改代码修复诊断出的缺陷用 `bug-fix`；需要核对业务数据状态用 `db-query`（生产只读）；需要评审提交或核对缺陷由哪次提交引入用 `code-review`；前端（浏览器侧）报错用 `frontend-error-diagnose`。
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
- frontend-error-diagnoseSkill
- git-clean-branchesSkill
- git-history-rewriteSkill
- git-rollbackSkill
- git-worktreeSkill
- i18n-transformSkill
- 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.