跳到主要内容
知仓学习社ZHICANG

learn-rule

Capture a correction or lesson as a persistent learning rule with category, mistake, and correction. Stores, categorises, and retrieves rules for fu…

不碰外部(只输出文字)无严重或高危命中rohitg00/pro-workflow

它会碰到什么

扫了多少1 个文本文件,2 KB
它会碰到什么不碰外部(只输出文字)
命中总数0 处
命中统计严重 0 · 高 0 · 中 0 · 低 0

这一栏是扫描器报的事实,不是结论。命中多不等于有毒(安全工具、规则库、示例脚本本来就会包含危险写法),命中少也不等于干净。它和你手上的凭据、文件、网络有什么关系,需要你自己看。

技能内容

Learn Rule

Capture a lesson from the current session into permanent memory.

Trigger

Use when the user says "remember this", "add to rules", "don't do that again", or after a mistake is identified.

Workflow

  1. Identify the lesson — what mistake was made? What should happen instead?
  2. Format the rule with full context.
  3. Propose the addition and wait for user approval.
  4. After approval, persist to LEARNED section or project memory.

Format

[LEARN] Category: One-line rule
Mistake: What went wrong
Correction: How it was fixed

Wiki-scoped rules

Append Wiki: <slug> to bind the rule to a single pro-workflow wiki. The rule loads only when that wiki is in scope, avoiding cross-project pollution:

[LEARN] Editing: Cite a sources.md row before adding any wiki claim.
Wiki: agent-memory

The capture hook auto-detects Wiki: <slug> and links the learning to that wiki via learnings_wiki.

Categories

| Category | Examples |

|----------|---------|

| Navigation | File paths, finding code, wrong file edited |

| Editing | Code changes, patterns, wrong approach |

| Testing | Test approaches, coverage gaps, flaky tests |

| Git | Commits, branches, merge issues |

| Quality | Lint, types, style violations |

| Context | When to clarify, missing requirements |

| Architecture | Design decisions, wrong abstractions |

| Performance | Optimization, O(n^2) loops, memory |

Example

Recent mistake: Edited wrong utils.ts file

[LEARN] Navigation: Confirm full path when multiple files share a name.

Add to LEARNED section? (y/n)

Guardrails

  • Always wait for user approval before persisting.
  • Keep rules to one line — specific and actionable.
  • Bad: "Write good code". Good: "Always use snake_case for database columns".
  • Include the mistake context so the rule makes sense later.

Output

  • The proposed [LEARN] rule with category
  • Confirmation after persisting

想直接用这个技能?

本站把开放许可(MIT / Apache 等)的技能按仓库打包整理到网盘,点一下转存到你自己的网盘,不用一个个从 GitHub 拉。许可未声明的技能只给原始仓库链接,不打包。