浏览器与自动化
smart-donkey-learn
Trigger Smart Donkey's learning phase: distill insights from the current session into smart-donkey-brain.md.
cloudyview · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add cloudyview/smart-donkey --skill smart-donkey-learn技能说明
name: smart-donkey-learn description: "Trigger Smart Donkey's learning phase: distill insights from the current session into smart-donkey-brain.md." user-invocable: true allowed-tools:
- Read
- Write
- Edit
- Bash
- Glob
- Grep
Smart Donkey Learn
Trigger the learning/distillation phase explicitly.
Steps
- Read current brain file (if exists):
cat smart-donkey-brain.md 2>/dev/null || echo "NO_BRAIN_FILE"
-
Read session context:
- Read
progress.mdfor what happened this session - Read
task_plan.mdfor decisions and errors - Read
findings.mdfor technical discoveries
- Read
-
Analyze the session for extractable lessons:
- What approaches worked well? (Save to "What Works Well")
- What mistakes were made and how were they fixed? (Save to "Mistakes to Avoid")
- Did the user express any preferences? (Save to "User Preferences")
- Any important codebase patterns discovered? (Save to "Codebase Patterns")
- Any debugging insights? (Save to "Debugging Playbook")
- Any architecture decisions made? (Save to "Architecture Notes")
-
Update
smart-donkey-brain.md:- If file doesn't exist, create it with the template
- If file exists, merge new lessons with existing ones
- Don't duplicate — update existing entries if refined
- Remove anything that's no longer accurate
- Keep total file under 200 lines
-
Present summary to user:
- Show what new lessons were extracted
- Show what existing lessons were updated
- Show total lesson count
Brain File Template
# Smart Donkey Brain
> Auto-generated learning file. Updated: [date]
> Sessions learned from: [N]
## User Preferences
(How the user likes to work)
## Codebase Patterns
(Key patterns, file paths, conventions)
## What Works Well
(Approaches that save time)
## Mistakes to Avoid
(Errors and their root causes)
## Architecture Notes
(Important design decisions)
## Debugging Playbook
(Issue pattern -> Solution approach)
Rules
- Be ruthlessly concise — 1-2 lines per entry
- Only save lessons that will be useful in FUTURE sessions
- Don't save task-specific details (they belong in progress.md)
- Facts > opinions. Mark uncertain items with "(uncertain)"
- If the brain file is over 200 lines, prune the least valuable entries