feedback-learning

Classify and record corrective feedback into tests, design documents, instructions, or learning inboxes.

10|1|Updated Jul 13, 2026
One-click install
npx skills add https://github.com/KevinHuangIsLearning/shortestpath-ide --skill feedback-learning-kevinhuangislearning
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feedback-learning
Source: https://github.com/KevinHuangIsLearning/shortestpath-ide/tree/main/.github/skills/feedback-learning
Command: npx skills add https://github.com/KevinHuangIsLearning/shortestpath-ide --skill feedback-learning-kevinhuangislearning

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When users correct an agent's implementation or design approach, that knowledge is often lost or dumped into ever-growing instruction files. This Skill routes each correction to the smallest authoritative destination so reusable knowledge is preserved without turning skills and instructions into append-only knowledge dumps. ## Core Features & Use Cases - Feedback classification: Routes corrections to the right destination — regression tests for concrete behavior, design documents for architectural invariants, instruction files for universal rules, or .github/learnings/<area>.md inboxes for immature guidance. - Duplicate prevention: Searches existing instructions, skills, design documents, and tests before writing, updating existing rules instead of adding duplicates. - Inbox maintenance: Enforces a ten-topic, 8 KB limit per learning inbox with compaction, promotion, and garbage-collection rules including a 90-day review cycle. - Use Case: A user rejects an agent's error-handling pattern in a subsystem. The skill generalizes the principle, checks for an existing rule, and records it once in the owning design document or a scoped learning inbox entry with scope, evidence, and disposition fields. ## Quick Start When I correct your approach or reject a pattern, classify my feedback and record it in the appropriate destination following the feedback-learning workflow.

Frequently Asked Questions about feedback-learning

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

FAQPage Schema
How do I make an AI agent remember my corrections?▼

State your correction explicitly, including what was wrong and the preferred approach. The skill classifies the feedback and records it once in the appropriate destination, such as a regression test, design document, instruction file, or scoped learning inbox.

Where should reusable feedback be stored in a repository?▼

Storage depends on the feedback kind: concrete behavior goes into regression tests, architectural invariants into design documents, universal rules into instruction files, and immature guidance into .github/learnings/<area>.md inbox files.

Does this skill handle the learn! command?▼

No. Literal learn! requests are governed exclusively by .github/instructions/learnings.instructions.md and are outside this skill's scope. The skill only handles explicit corrections, rejected patterns, and general learn-from-feedback requests.

How are learning inbox files kept from growing indefinitely?▼

Each area inbox is limited to ten topics and 8 KB. Entries are compacted before every write, and a full review occurs when limits are reached or the Last reviewed date exceeds 90 days, promoting, merging, or removing entries.

When should feedback not be persisted at all?▼

Task-specific preferences and one-off adjustments are not persisted. A single rejected implementation should not become a universal prohibition without broader evidence, and temporary details like line numbers are excluded from recorded rules.