feedback-learning

Classify and record explicit corrective feedback into appropriate repository artifacts.

190k|41.9k|Updated Sep 3, 2015
One-click install
npx skills add https://github.com/microsoft/vscode --skill feedback-learning
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feedback-learning
Source: https://github.com/microsoft/vscode/tree/main/.github/skills/feedback-learning
Command: npx skills add https://github.com/microsoft/vscode --skill feedback-learning

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers and AI agents often receive corrective feedback during implementation but lack a structured way to decide whether that feedback should become a permanent rule, a test, a design note, or be discarded. This Skill prevents skills and instructions from becoming append-only knowledge dumps by enforcing classification and compaction rules.

Core Features & Use Cases

  • Feedback Classification: Routes corrections to the correct destination: regression tests, design documents, instruction files, learning inboxes, or skills.
  • Learning Inbox Management: Creates and maintains .github/learnings/<area>.md files with strict size and entry limits, including compaction and garbage collection rules.
  • Use Case: When a user rejects a specific implementation pattern during code review, use this Skill to determine whether the correction is a one-off preference, a regression test case, or a stable architectural invariant that belongs in a design document.

Quick Start

Apply the feedback-learning skill to classify this user correction and record it in the appropriate repository artifact.

Frequently Asked Questions about feedback-learning

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

FAQPage Schema
How do I record user feedback in a repository without bloating instructions?

Classify the feedback first: one-off preferences are not persisted, concrete behaviors become regression tests, stable invariants go into design documents, and reusable but unproven guidance goes into a scoped learning inbox file.

What is a learning inbox file in GitHub repositories?

A learning inbox is a temporary Markdown file under `.github/learnings/<area>.md` that holds reusable but not yet mature guidance. Each inbox is capped at ten topics and 8 KB and must be compacted or promoted regularly.

When should feedback become a regression test versus a design document?

Encode concrete behavior that must not regress as a regression test. Promote stable subsystem architecture or product invariants into the relevant design or specification document instead of duplicating them into instructions.

Why are learning inbox entries removed after promotion?

Design documents and tests are authoritative sources. Keeping the inbox entry after promotion creates duplicate rules across skills, instructions, and design documents, which violates the single-source-of-truth principle.

What is the difference between feedback-learning and the learn! trigger?

The feedback-learning skill handles explicit corrective feedback during normal work. Literal `learn!` requests are governed exclusively by `.github/instructions/learnings.instructions.md` and are outside this skill's scope.