技能提高者
- 作者仓库星标 267
- 作者仓库 mini-diarium
- 领域
- 人工智能
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @fjrevoredo · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 需简单配置
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- macOS · Linux · Windows
- 运行环境要求
- Node.js
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 命令执行
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
第 1 步——反思
将观察结果分为三个部分,并附有具体示例: 哪些进展顺利:节省时间或防止错误的模式、工具或决策 事实证明特别有用的技能说明 快速诊断或修复
第 2 步 — 分类
将调查结果分为三类。对于每个发现,确定需要更改的具体工件(文件路径、技能部分、CI 工作流程等)。技能变更 — 对现有技能的改进: 诊断表中缺少故障条目 错误的修复说明
第 3 步 — 申请
如果没有发现任何改进:明确说明并停止。不要发明改变。用户始终可以推翻计划/执行决策。如果用户对通常需要计划的内容说“直接修复它”,请直接应用更改。如果用户说为一些小事情“制定一个计划”,那就创建一个。对于明显的修复(拼写错误、缺少警告、不完整的说明):
第 4 步 — 验证
应用修复后(直接或通过计划执行): 如果更改的文件采用已检查的语言,则运行 format/lint 命令 对于脚本,运行语法检查和快速冒烟测试 重新阅读更改的技能部分,以确保它们与技能的其他部分或相邻技能不矛盾 总结更改的内容以及原因
# Skill Improver
Turn every hard-earned lesson into a reusable improvement. After completing a non-trivial task
(especially one that hit friction), run this skill to catalog what happened, classify the gaps,
and apply fixes — either directly for obvious issues, or via a structured plan for larger changes.
## When to Run
**Proactive (run without being asked):**
- A build, deploy, or CI job failed and was debugged
- A task took more than 3 rounds of trial-and-error
- A session lasted more than one hour and involved multiple skill uses
- The user explicitly expressed frustration or surprise at a gap
**On-demand (run when the user says):**
- "Reflect on this session" / "post-mortem" / "what went wrong"
- "Improve the skill" / "update the skill with these learnings"
- "Lessons learned" / "what should we change"
**Scope:** Reflect on ALL skills used during the session, plus any repo artifacts
and process steps involved. If multiple skills were loaded, review each one.
If the session didn't use any skill, focus on repo/process improvements only.
## Workflow
### Step 1 — Reflect
Catalog observations in three buckets, with concrete examples:
**What went well:**
- Patterns, tools, or decisions that saved time or prevented errors
- Skill instructions that proved particularly useful
- Diagnoses or fixes that were reached quickly
**What went wrong:**
- Mistakes, dead ends, or incorrect assumptions
- Skill instructions that were missing, wrong, or misleading
- Manual workarounds that had to be invented on the fly
**What was missing:**
- Scripts, checks, or tooling that would have caught the issue earlier
- Documentation or guardrails that didn't exist
- Process steps that were skipped or not automated
### Step 2 — Classify
Group findings into three categories. For each finding, identify the concrete artifact
that needs to change (file path, skill section, CI workflow, etc.).
**Skill changes** — improvements to an existing skill:
- Missing failure entries in a diagnosis table
- Wrong fix instructions
- Undocumented pitfalls or edge cases
- Better log access or debugging workflows
**Repo artifact changes** — new or modified files in the repository:
- Utility scripts (e.g., `check-node-sources.mjs`)
- CI workflow steps or pre-release checks
- Configuration or lockfile validation
**Process changes** — workflow or convention changes:
- Release checklist items
- Pre-commit or pre-tag validation steps
- Cross-skill integration (e.g., pre-release skill should validate lockfiles)
### Step 3 — Apply
**If no improvements are identified:** state that explicitly and stop. Do not invent changes.
**The user can always override the plan/execute decision.** If the user says "just fix it directly" for something that would normally need a plan, apply the changes directly instead. If the user says "make a plan" for something small, create one.
**For obvious fixes (typos, missing warnings, incomplete instructions):**
Apply directly to the target file using the Edit tool. These are changes where:
- The fix is a single addition or correction to an existing section
- There's no design decision to make
- The change can't break anything else
- Example: adding a missing failure entry to a diagnosis table, or a warning about a known pitfall
**For structural changes (new sections, new scripts, reorganized workflows):**
Create a plan using the manual-planning skill's format. These are changes where:
- The fix requires creating a new file or reorganizing existing content
- Multiple files are affected
- The user should review the approach before implementation
- Example: adding a new utility script, restructuring a skill's diagnosis workflow, adding pre-release steps
### Step 4 — Verify
After applying fixes (directly or via plan execution):
1. Run format/lint commands if the changed files are in checked languages
2. For scripts, run a syntax check and a quick smoke test
3. Re-read the changed skill sections to ensure they don't contradict other parts of the skill or adjacent skills
4. Summarize what was changed and why
## Output Format
At the end, present using this template:
```
## Session Reflection
### What Went Well
- [item]
### What Went Wrong
- [item]
### What Was Missing
- [item]
## Changes Made
| File | Change |
|------|--------|
| path/to/file | what changed and why |
<!-- If no changes were made: -->
No improvements identified.
```
If a plan was created, add: `**Plan:** docs/plan-name.md — awaiting approval.`
## Gotchas
- **Don't over-improve.** If the session went smoothly and no concrete gaps were found, say so and stop. Inventing minor tweaks dilutes the skill.
- **One session, one reflection.** Don't chain multiple reflection cycles. If the user wants another, they'll ask.
- **Obvious fix ≠ trivial preference.** "I'd word this differently" is a preference, not a fix. Only apply direct edits when the current text is objectively wrong or missing.
- **Respect the user's override.** If the user says "just fix it" for something structural, apply directly. If they say "make a plan" for something small, create one. Their call always wins.
## Integration with Other Skills
- Use **manual-planning** for any change that needs a plan (structural changes)
- Use **todo-manager** if the reflection surfaces new TODO items for the backlog
- The output format mirrors what you'd see in a good commit message: what, why, and where
章节与文件索引
按说明文件中的顺序排列。
何时跑步
第 1 步——反思
第 2 步 — 分类
第 3 步 — 申请
第 4 步 — 验证
文件/命令 -> check-node-sources.mjs · **Plan:** docs/plan-name.md — awaiting approval. · repo/process · plan/execute · format/lint · path/to/file · docs/plan-name.md
内容校验值 -> 25490ab20c97
当前原文的自动摘译,尚未人工审校。
何时跑步
主动(无需询问即可运行):构建、部署或 CI 作业失败并已调试 任务进行了 3 轮以上的试错 会话持续超过 1 小时并涉及多种技能使用 用户明确表达了对差距的沮丧或惊讶