learn-rule

Captures corrections and lessons as persistent categorized learning rules for future sessions.

2.8k|277|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/rohitg00/pro-workflow --skill learn-rule
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: learn-rule
Source: https://github.com/rohitg00/pro-workflow/tree/main/skills/learn-rule
Command: npx skills add https://github.com/rohitg00/pro-workflow --skill learn-rule

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

AI coding assistants repeat the same mistakes across sessions because corrections vanish when context resets. This Skill turns every correction into a durable, searchable rule so the assistant never repeats the same error.

Core Features & Use Cases

  • Rule Capture Workflow: Identifies the mistake, formats it as a one-line rule with mistake and correction context, and proposes it for user approval before persisting.
  • Categorized Learnings: Organizes rules into eight categories including Navigation, Editing, Testing, Git, Quality, Context, Architecture, and Performance.
  • Wiki-Scoped Rules: Binds a rule to a specific pro-workflow wiki via a Wiki slug so it only loads when that wiki is in scope, avoiding cross-project pollution.
  • Use Case: After the assistant edits the wrong utils.ts file, say "remember this" and it proposes a Navigation rule requiring full path confirmation, which loads automatically in future sessions.

Quick Start

Tell the assistant to remember this correction and save it as a learning rule for future sessions.

Frequently Asked Questions about learn-rule

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make an AI assistant remember a correction permanently?

Say "remember this" or "don't do that again" after a mistake. The assistant formats the lesson as a one-line rule with category, mistake, and correction, then asks for your approval before saving it to persistent memory.

What categories can learning rules be organized into?

Rules are grouped into eight categories: Navigation, Editing, Testing, Git, Quality, Context, Architecture, and Performance. Each rule is a single specific, actionable line such as "Always use snake_case for database columns."

Can I scope a learning rule to a single project or wiki?

Yes. Append "Wiki: <slug>" to the rule and the capture hook links it to that pro-workflow wiki via learnings_wiki. The rule then loads only when that wiki is in scope, preventing cross-project pollution.

Does the skill save rules automatically without confirmation?

No. The workflow always proposes the formatted rule and waits for explicit user approval before persisting it to the LEARNED section or project memory. This guardrail prevents unwanted or incorrect rules from being stored.

What makes a good learning rule versus a bad one?

Good rules are one line, specific, and actionable, like "Confirm full path when multiple files share a name." Vague rules like "Write good code" are rejected because they cannot be applied consistently in future sessions.