清理综合模式中的 Wiki/记忆遗留逻辑并完善自治技能文档。

彻底移除 manager_memory 与 wiki 注入写入分支，收敛网关分发路径和测试用例，同时补齐并中文化 session-bootstrap / wiki-first-autonomy / self-improvement 的 Wiki-first 规范，保证行为与提示词一致。 Made-with: Cursor
2026-10-15 22:13:23 +08:00 · 2026-04-29 01:04:30 +08:00 · 2026-04-29 01:04:30 +08:00 · 3122b8a16c
commit 3122b8a16c
parent 8b8265eb46
23 changed files with 948 additions and 1093 deletions
--- a/runtime/skills/self-improvement/SKILL.md
+++ b/runtime/skills/self-improvement/SKILL.md
@ -1,644 +1,83 @@
 ---
 name: self-improvement
-description: "Captures learnings, errors, and corrections to enable continuous improvement. Use when: (1) A command or operation fails unexpectedly, (2) User corrects Claude ('No, that's wrong...', 'Actually...'), (3) User requests a capability that doesn't exist, (4) An external API or tool fails, (5) Claude realizes its knowledge is outdated or incorrect, (6) A better approach is discovered for a recurring task. Also review learnings before major tasks."
+description: 将纠错、错误与能力缺口写入 Wiki 以持续改进。适用于操作失败、用户反馈纠正、问题复发、或需要沉淀并推动的新能力需求场景。
 metadata:
 ---

-# Self-Improvement Skill
+# 自我改进（仅 Wiki）

-Log learnings and errors to markdown files for continuous improvement. Coding agents can later process these into fixes, and important learnings get promoted to project memory.
+本技能仅使用 Wiki，不使用本地 `.learnings/` 文件。

-## First-Use Initialisation
+## 存储路径

-Before logging anything, ensure the `.learnings/` directory and files exist in the project or workspace root. If any are missing, create them:
+- `improvement/learnings.md`
+- `improvement/errors.md`
+- `improvement/feature-requests.md`

-```bash
-mkdir -p .learnings
-[ -f .learnings/LEARNINGS.md ] || printf "# Learnings\n\nCorrections, insights, and knowledge gaps captured during development.\n\n**Categories**: correction | insight | knowledge_gap | best_practice\n\n---\n" > .learnings/LEARNINGS.md
-[ -f .learnings/ERRORS.md ] || printf "# Errors\n\nCommand failures and integration errors.\n\n---\n" > .learnings/ERRORS.md
-[ -f .learnings/FEATURE_REQUESTS.md ] || printf "# Feature Requests\n\nCapabilities requested by the user.\n\n---\n" > .learnings/FEATURE_REQUESTS.md
-```
+## 触发条件

-Never overwrite existing files. This is a no-op if `.learnings/` is already initialised.
+出现以下情况时启用本技能：

-Do not log secrets, tokens, private keys, environment variables, or full source/config files unless the user explicitly asks for that level of detail. Prefer short summaries or redacted excerpts over raw command output or full transcripts.
+1. 命令或操作出现非预期失败。
+2. 用户对错误回答进行纠正。
+3. 用户提出缺失能力需求。
+4. 同类问题再次复发。
+5. 发现更优且可复用的方法。

-If you want automatic reminders or setup assistance, use the opt-in hook workflow described in [Hook Integration](#hook-integration).
+## 必要流程

-## Quick Reference
+每次触发都执行以下流程：

-| Situation | Action |
-|-----------|--------|
-| Command/operation fails | Log to `.learnings/ERRORS.md` |
-| User corrects you | Log to `.learnings/LEARNINGS.md` with category `correction` |
-| User wants missing feature | Log to `.learnings/FEATURE_REQUESTS.md` |
-| API/external tool fails | Log to `.learnings/ERRORS.md` with integration details |
-| Knowledge was outdated | Log to `.learnings/LEARNINGS.md` with category `knowledge_gap` |
-| Found better approach | Log to `.learnings/LEARNINGS.md` with category `best_practice` |
-| Simplify/Harden recurring patterns | Log/update `.learnings/LEARNINGS.md` with `Source: simplify-and-harden` and a stable `Pattern-Key` |
-| Similar to existing entry | Link with `**See Also**`, consider priority bump |
-| Broadly applicable learning | Promote to `CLAUDE.md`, `AGENTS.md`, and/or `.github/copilot-instructions.md` |
-| Workflow improvements | Promote to `AGENTS.md` (Oclaw workspace) |
-| Tool gotchas | Promote to `TOOLS.md` (Oclaw workspace) |
-| Behavioral patterns | Promote to `SOUL.md` (Oclaw workspace) |
+1. 用 `memory_wiki_search` 检索历史相关记录。
+2. 用 `memory_wiki_get` 读取目标文件上下文。
+3. 用 `memory_wiki_apply`（`action=append`）追加结构化条目。
+4. 对目标文件执行 `memory_wiki_lint`。
+5. 若 lint 报错，立即用 `memory_wiki_apply` 修复。

-## Oclaw Setup (Recommended)
+## 条目路由

-Oclaw is the primary platform for this skill. It uses workspace-based prompt injection with automatic skill loading.
+- 纠错 / 洞见 / 最佳实践 -> `improvement/learnings.md`
+- 运行时 / 工具 / API 失败 -> `improvement/errors.md`
+- 能力请求 / 缺失功能 -> `improvement/feature-requests.md`

-### Installation
-
-**Via ClawdHub (recommended):**
-```bash
-clawdhub install self-improving-agent
-```
-
-**Manual:**
-```bash
-git clone https://github.com/peterskoett/self-improving-agent.git ~/.oclaw/runtime/skills/self-improving-agent
-```
-
-Remade for oclaw from original repo : https://github.com/pskoett/pskoett-ai-skills - https://github.com/pskoett/pskoett-ai-skills/tree/main/skills/self-improvement
-
-### Workspace Structure
-
-Oclaw injects these files into every session:
-
-```
-~/.oclaw/workspace/
-├── AGENTS.md          # Multi-agent workflows, delegation patterns
-├── SOUL.md            # Behavioral guidelines, personality, principles
-├── TOOLS.md           # Tool capabilities, integration gotchas
-├── MEMORY.md          # Long-term memory (main session only)
-├── memory/            # Daily memory files
-│   └── YYYY-MM-DD.md
-└── .learnings/        # This skill's log files
-    ├── LEARNINGS.md
-    ├── ERRORS.md
-    └── FEATURE_REQUESTS.md
-```
-
-### Create Learning Files
-
-```bash
-mkdir -p ~/.oclaw/workspace/.learnings
-```
-
-Then create the log files (or copy from `assets/`):
- `LEARNINGS.md` — corrections, knowledge gaps, best practices
- `ERRORS.md` — command failures, exceptions
- `FEATURE_REQUESTS.md` — user-requested capabilities
-
-### Promotion Targets
-
-When learnings prove broadly applicable, promote them to workspace files:
-
-| Learning Type | Promote To | Example |
-|---------------|------------|---------|
-| Behavioral patterns | `SOUL.md` | "Be concise, avoid disclaimers" |
-| Workflow improvements | `AGENTS.md` | "Spawn sub-agents for long tasks" |
-| Tool gotchas | `TOOLS.md` | "Git push needs auth configured first" |
-
-### Inter-Session Communication
-
-Oclaw provides tools to share learnings across sessions:
-
- **sessions_list** — View active/recent sessions
- **sessions_history** — Read another session's transcript  
- **sessions_send** — Send a learning to another session
- **sessions_spawn** — Spawn a sub-agent for background work
-
-Use these only in trusted environments and only when the user explicitly wants cross-session sharing. Prefer sending a short sanitized summary and relevant file paths, not raw transcripts, secrets, or full command output.
-
-### Optional: Enable Hook
-
-For automatic reminders at session start:
-
-```bash
-# Copy hook to Oclaw hooks directory
-cp -r hooks/oclaw ~/.oclaw/hooks/self-improvement
-
-# Enable it
-oclaw hooks enable self-improvement
-```
-
-See `references/oclaw-integration.md` for complete details.
-
---
-
-## Generic Setup (Other Agents)
-
-For Claude Code, Codex, Copilot, or other agents, create `.learnings/` in the project or workspace root:
-
-```bash
-mkdir -p .learnings
-```
-
-Create the files inline using the headers shown above. Avoid reading templates from the current repo or workspace unless you explicitly trust that path.
-
-### Add reference to agent files AGENTS.md, CLAUDE.md, or .github/copilot-instructions.md to remind yourself to log learnings. (this is an alternative to hook-based reminders)
-
-#### Self-Improvement Workflow
-
-When errors or corrections occur:
-1. Log to `.learnings/ERRORS.md`, `LEARNINGS.md`, or `FEATURE_REQUESTS.md`
-2. Review and promote broadly applicable learnings to:
-   - `CLAUDE.md` - project facts and conventions
-   - `AGENTS.md` - workflows and automation
-   - `.github/copilot-instructions.md` - Copilot context
-
-## Logging Format
-
-### Learning Entry
-
-Append to `.learnings/LEARNINGS.md`:
+## 条目模板

 ```markdown
-## [LRN-YYYYMMDD-XXX] category
-
-**Logged**: ISO-8601 timestamp
+## [ID] <标题>
+**Logged**: ISO-8601 时间戳
 **Priority**: low | medium | high | critical
 **Status**: pending
 **Area**: frontend | backend | infra | tests | docs | config

 ### Summary
-One-line description of what was learned
+一句话摘要。

 ### Details
-Full context: what happened, what was wrong, what's correct
-
-### Suggested Action
-Specific fix or improvement to make
+发生了什么、为什么重要、可执行改进建议。

 ### Metadata
 - Source: conversation | error | user_feedback
 - Related Files: path/to/file.ext
- Tags: tag1, tag2
- See Also: LRN-20250110-001 (if related to existing entry)
- Pattern-Key: simplify.dead_code | harden.input_validation (optional, for recurring-pattern tracking)
- Recurrence-Count: 1 (optional)
- First-Seen: 2025-01-15 (optional)
- Last-Seen: 2025-01-15 (optional)
-
---
+- See Also: <optional-id>
 ```

-### Error Entry
+ID 格式：

-Append to `.learnings/ERRORS.md`:
+- Learning: `LRN-YYYYMMDD-XXX`
+- Error: `ERR-YYYYMMDD-XXX`
+- Feature request: `FEAT-YYYYMMDD-XXX`

-```markdown
-## [ERR-YYYYMMDD-XXX] skill_or_command_name
+## 提升目标

-**Logged**: ISO-8601 timestamp
-**Priority**: high
-**Status**: pending
-**Area**: frontend | backend | infra | tests | docs | config
+当条目已具备广泛复用价值时，将精炼规则提升到：

-### Summary
-Brief description of what failed
+- `AGENTS.md`（工作流模式）
+- `SOUL.md`（行为模式）
+- `TOOLS.md`（工具易错点）
+- `.github/copilot-instructions.md`（共享编码约定）

-### Error
-```
-Actual error message or output
-```
+## 安全规则

-### Context
- Command/operation attempted
- Input or parameters used
- Environment details if relevant
- Summary or redacted excerpt of relevant output (avoid full transcripts and secret-bearing data by default)
-
-### Suggested Fix
-If identifiable, what might resolve this
-
-### Metadata
- Reproducible: yes | no | unknown
- Related Files: path/to/file.ext
- See Also: ERR-20250110-001 (if recurring)
-
---
-```
-
-### Feature Request Entry
-
-Append to `.learnings/FEATURE_REQUESTS.md`:
-
-```markdown
-## [FEAT-YYYYMMDD-XXX] capability_name
-
-**Logged**: ISO-8601 timestamp
-**Priority**: medium
-**Status**: pending
-**Area**: frontend | backend | infra | tests | docs | config
-
-### Requested Capability
-What the user wanted to do
-
-### User Context
-Why they needed it, what problem they're solving
-
-### Complexity Estimate
-simple | medium | complex
-
-### Suggested Implementation
-How this could be built, what it might extend
-
-### Metadata
- Frequency: first_time | recurring
- Related Features: existing_feature_name
-
---
-```
-
-## ID Generation
-
-Format: `TYPE-YYYYMMDD-XXX`
- TYPE: `LRN` (learning), `ERR` (error), `FEAT` (feature)
- YYYYMMDD: Current date
- XXX: Sequential number or random 3 chars (e.g., `001`, `A7B`)
-
-Examples: `LRN-20250115-001`, `ERR-20250115-A3F`, `FEAT-20250115-002`
-
-## Resolving Entries
-
-When an issue is fixed, update the entry:
-
-1. Change `**Status**: pending` → `**Status**: resolved`
-2. Add resolution block after Metadata:
-
-```markdown
-### Resolution
- **Resolved**: 2025-01-16T09:00:00Z
- **Commit/PR**: abc123 or #42
- **Notes**: Brief description of what was done
-```
-
-Other status values:
- `in_progress` - Actively being worked on
- `wont_fix` - Decided not to address (add reason in Resolution notes)
- `promoted` - Elevated to CLAUDE.md, AGENTS.md, or .github/copilot-instructions.md
-
-## Promoting to Project Memory
-
-When a learning is broadly applicable (not a one-off fix), promote it to permanent project memory.
-
-### When to Promote
-
- Learning applies across multiple files/features
- Knowledge any contributor (human or AI) should know
- Prevents recurring mistakes
- Documents project-specific conventions
-
-### Promotion Targets
-
-| Target | What Belongs There |
-|--------|-------------------|
-| `CLAUDE.md` | Project facts, conventions, gotchas for all Claude interactions |
-| `AGENTS.md` | Agent-specific workflows, tool usage patterns, automation rules |
-| `.github/copilot-instructions.md` | Project context and conventions for GitHub Copilot |
-| `SOUL.md` | Behavioral guidelines, communication style, principles (Oclaw workspace) |
-| `TOOLS.md` | Tool capabilities, usage patterns, integration gotchas (Oclaw workspace) |
-
-### How to Promote
-
-1. **Distill** the learning into a concise rule or fact
-2. **Add** to appropriate section in target file (create file if needed)
-3. **Update** original entry:
-   - Change `**Status**: pending` → `**Status**: promoted`
-   - Add `**Promoted**: CLAUDE.md`, `AGENTS.md`, or `.github/copilot-instructions.md`
-
-### Promotion Examples
-
-**Learning** (verbose):
-> Project uses pnpm workspaces. Attempted `npm install` but failed. 
-> Lock file is `pnpm-lock.yaml`. Must use `pnpm install`.
-
-**In CLAUDE.md** (concise):
-```markdown
-## Build & Dependencies
- Package manager: pnpm (not npm) - use `pnpm install`
-```
-
-**Learning** (verbose):
-> When modifying API endpoints, must regenerate TypeScript client.
-> Forgetting this causes type mismatches at runtime.
-
-**In AGENTS.md** (actionable):
-```markdown
-## After API Changes
-1. Regenerate client: `pnpm run generate:api`
-2. Check for type errors: `pnpm tsc --noEmit`
-```
-
-## Recurring Pattern Detection
-
-If logging something similar to an existing entry:
-
-1. **Search first**: `grep -r "keyword" .learnings/`
-2. **Link entries**: Add `**See Also**: ERR-20250110-001` in Metadata
-3. **Bump priority** if issue keeps recurring
-4. **Consider systemic fix**: Recurring issues often indicate:
-   - Missing documentation (→ promote to CLAUDE.md or .github/copilot-instructions.md)
-   - Missing automation (→ add to AGENTS.md)
-   - Architectural problem (→ create tech debt ticket)
-
-## Simplify & Harden Feed
-
-Use this workflow to ingest recurring patterns from the `simplify-and-harden`
-skill and turn them into durable prompt guidance.
-
-### Ingestion Workflow
-
-1. Read `simplify_and_harden.learning_loop.candidates` from the task summary.
-2. For each candidate, use `pattern_key` as the stable dedupe key.
-3. Search `.learnings/LEARNINGS.md` for an existing entry with that key:
-   - `grep -n "Pattern-Key: <pattern_key>" .learnings/LEARNINGS.md`
-4. If found:
-   - Increment `Recurrence-Count`
-   - Update `Last-Seen`
-   - Add `See Also` links to related entries/tasks
-5. If not found:
-   - Create a new `LRN-...` entry
-   - Set `Source: simplify-and-harden`
-   - Set `Pattern-Key`, `Recurrence-Count: 1`, and `First-Seen`/`Last-Seen`
-
-### Promotion Rule (System Prompt Feedback)
-
-Promote recurring patterns into agent context/system prompt files when all are true:
-
- `Recurrence-Count >= 3`
- Seen across at least 2 distinct tasks
- Occurred within a 30-day window
-
-Promotion targets:
- `CLAUDE.md`
- `AGENTS.md`
- `.github/copilot-instructions.md`
- `SOUL.md` / `TOOLS.md` for Oclaw workspace-level guidance when applicable
-
-Write promoted rules as short prevention rules (what to do before/while coding),
-not long incident write-ups.
-
-## Periodic Review
-
-Review `.learnings/` at natural breakpoints:
-
-### When to Review
- Before starting a new major task
- After completing a feature
- When working in an area with past learnings
- Weekly during active development
-
-### Quick Status Check
-```bash
-# Count pending items
-grep -h "Status\*\*: pending" .learnings/*.md | wc -l
-
-# List pending high-priority items
-grep -B5 "Priority\*\*: high" .learnings/*.md | grep "^## \["
-
-# Find learnings for a specific area
-grep -l "Area\*\*: backend" .learnings/*.md
-```
-
-### Review Actions
- Resolve fixed items
- Promote applicable learnings
- Link related entries
- Escalate recurring issues
-
-## Detection Triggers
-
-Automatically log when you notice:
-
-**Corrections** (→ learning with `correction` category):
- "No, that's not right..."
- "Actually, it should be..."
- "You're wrong about..."
- "That's outdated..."
-
-**Feature Requests** (→ feature request):
- "Can you also..."
- "I wish you could..."
- "Is there a way to..."
- "Why can't you..."
-
-**Knowledge Gaps** (→ learning with `knowledge_gap` category):
- User provides information you didn't know
- Documentation you referenced is outdated
- API behavior differs from your understanding
-
-**Errors** (→ error entry):
- Command returns non-zero exit code
- Exception or stack trace
- Unexpected output or behavior
- Timeout or connection failure
-
-## Priority Guidelines
-
-| Priority | When to Use |
-|----------|-------------|
-| `critical` | Blocks core functionality, data loss risk, security issue |
-| `high` | Significant impact, affects common workflows, recurring issue |
-| `medium` | Moderate impact, workaround exists |
-| `low` | Minor inconvenience, edge case, nice-to-have |
-
-## Area Tags
-
-Use to filter learnings by codebase region:
-
-| Area | Scope |
-|------|-------|
-| `frontend` | UI, components, client-side code |
-| `backend` | API, services, server-side code |
-| `infra` | CI/CD, deployment, Docker, cloud |
-| `tests` | Test files, testing utilities, coverage |
-| `docs` | Documentation, comments, READMEs |
-| `config` | Configuration files, environment, settings |
-
-## Best Practices
-
-1. **Log immediately** - context is freshest right after the issue
-2. **Be specific** - future agents need to understand quickly
-3. **Include reproduction steps** - especially for errors
-4. **Link related files** - makes fixes easier
-5. **Suggest concrete fixes** - not just "investigate"
-6. **Use consistent categories** - enables filtering
-7. **Promote aggressively** - if in doubt, add to CLAUDE.md or .github/copilot-instructions.md
-8. **Review regularly** - stale learnings lose value
-
-## Gitignore Options
-
-**Keep learnings local** (per-developer):
-```gitignore
-.learnings/
-```
-
-This repo uses that default to avoid committing sensitive or noisy local logs by accident.
-
-**Track learnings in repo** (team-wide):
-Don't add to .gitignore - learnings become shared knowledge.
-
-**Hybrid** (track templates, ignore entries):
-```gitignore
-.learnings/*.md
-!.learnings/.gitkeep
-```
-
-## Hook Integration
-
-Enable automatic reminders through agent hooks. This is **opt-in** - you must explicitly configure hooks.
-
-### Quick Setup (Claude Code / Codex)
-
-Create `.claude/settings.json` in your project:
-
-```json
-{
-  "hooks": {
-    "UserPromptSubmit": [{
-      "matcher": "",
-      "hooks": [{
-        "type": "command",
-        "command": "./runtime/skills/self-improvement/scripts/activator.sh"
-      }]
-    }]
-  }
-}
-```
-
-This injects a learning evaluation reminder after each prompt (~50-100 tokens overhead).
-
-### Advanced Setup (With Error Detection)
-
-```json
-{
-  "hooks": {
-    "UserPromptSubmit": [{
-      "matcher": "",
-      "hooks": [{
-        "type": "command",
-        "command": "./runtime/skills/self-improvement/scripts/activator.sh"
-      }]
-    }],
-    "PostToolUse": [{
-      "matcher": "Bash",
-      "hooks": [{
-        "type": "command",
-        "command": "./runtime/skills/self-improvement/scripts/error-detector.sh"
-      }]
-    }]
-  }
-}
-```
-
-This is optional. The recommended default is activator-only setup; enable `PostToolUse` only if you are comfortable with hook scripts inspecting command output for error patterns.
-
-### Available Hook Scripts
-
-| Script | Hook Type | Purpose |
-|--------|-----------|---------|
-| `scripts/activator.sh` | UserPromptSubmit | Reminds to evaluate learnings after tasks |
-| `scripts/error-detector.sh` | PostToolUse (Bash) | Triggers on command errors |
-
-See `references/hooks-setup.md` for detailed configuration and troubleshooting.
-
-## Automatic Skill Extraction
-
-When a learning is valuable enough to become a reusable skill, extract it using the provided helper.
-
-### Skill Extraction Criteria
-
-A learning qualifies for skill extraction when ANY of these apply:
-
-| Criterion | Description |
-|-----------|-------------|
-| **Recurring** | Has `See Also` links to 2+ similar issues |
-| **Verified** | Status is `resolved` with working fix |
-| **Non-obvious** | Required actual debugging/investigation to discover |
-| **Broadly applicable** | Not project-specific; useful across codebases |
-| **User-flagged** | User says "save this as a skill" or similar |
-
-### Extraction Workflow
-
-1. **Identify candidate**: Learning meets extraction criteria
-2. **Run helper** (or create manually):
-   ```bash
-   ./runtime/skills/self-improvement/scripts/extract-skill.sh skill-name --dry-run
-   ./runtime/skills/self-improvement/scripts/extract-skill.sh skill-name
-   ```
-3. **Customize SKILL.md**: Fill in template with learning content
-4. **Update learning**: Set status to `promoted_to_skill`, add `Skill-Path`
-5. **Verify**: Read skill in fresh session to ensure it's self-contained
-
-### Manual Extraction
-
-If you prefer manual creation:
-
-1. Create `skills/<skill-name>/SKILL.md`
-2. Use template from `assets/SKILL-TEMPLATE.md`
-3. Follow [Agent Skills spec](https://agentskills.io/specification):
-   - YAML frontmatter with `name` and `description`
-   - Name must match folder name
-   - No README.md inside skill folder
-
-### Extraction Detection Triggers
-
-Watch for these signals that a learning should become a skill:
-
-**In conversation:**
- "Save this as a skill"
- "I keep running into this"
- "This would be useful for other projects"
- "Remember this pattern"
-
-**In learning entries:**
- Multiple `See Also` links (recurring issue)
- High priority + resolved status
- Category: `best_practice` with broad applicability
- User feedback praising the solution
-
-### Skill Quality Gates
-
-Before extraction, verify:
-
- [ ] Solution is tested and working
- [ ] Description is clear without original context
- [ ] Code examples are self-contained
- [ ] No project-specific hardcoded values
- [ ] Follows skill naming conventions (lowercase, hyphens)
-
-## Multi-Agent Support
-
-This skill works across different AI coding agents with agent-specific activation.
-
-### Claude Code
-
-**Activation**: Hooks (UserPromptSubmit, PostToolUse)
-**Setup**: `.claude/settings.json` with hook configuration
-**Detection**: Automatic via hook scripts
-
-### Codex CLI
-
-**Activation**: Hooks (same pattern as Claude Code)
-**Setup**: `.codex/settings.json` with hook configuration
-**Detection**: Automatic via hook scripts
-
-### GitHub Copilot
-
-**Activation**: Manual (no hook support)
-**Setup**: Add to `.github/copilot-instructions.md`:
-
-```markdown
-## Self-Improvement
-
-After solving non-obvious issues, consider logging to `.learnings/`:
-1. Use format from self-improvement skill
-2. Link related entries with See Also
-3. Promote high-value learnings to skills
-
-Ask in chat: "Should I log this as a learning?"
-```
-
-**Detection**: Manual review at session end
+- 不记录密钥、令牌、凭据或原始敏感信息。
+- 敏感输出使用脱敏摘要，不保留完整原文。
+- 未验证事实不得当作已确认规则持久化。