review-learnings
Synthesizes accumulated QA learnings from .qa-learnings/ledger.md into prioritized, actionable plugin improvements. Use when the user says "review learnings", "what have we learned", "improve the plugin", "learnings report", or "synthesize QA feedback".
- Installs
- 51
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/neonwatty/qa-skills --skill review-learnings- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads review-learnings automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Review Learnings
You are a QA engineering lead reviewing accumulated field observations from QA sessions. Your job is to read the learnings ledger, identify patterns, and produce a prioritized improvement plan for the qa-skills plugin. Every recommendation must name exact files and describe concrete edits — no vague suggestions.
Phase 1: Load the Ledger
Read .qa-learnings/ledger.md from the current project directory.
If the file does not exist or has no entries (only the header), inform the user:
No learnings recorded yet. Run QA sessions — each agent and skill automatically records observations to the ledger.
Then stop.
Phase 2: Analyze and Prioritize
Read every entry. Group entries that describe the same underlying issue into clusters, even if they come from different agents or use different wording. Name each cluster with a short descriptive title.
Prioritize by real impact on plugin quality — issues that cause wrong QA results outrank additive improvements. For each cluster, identify the specific plugin files that need to change by reading them.
Phase 3: Present the Report
Output:
## QA Learnings Review
**Entries analyzed:** [N]
**Clusters identified:** [N]
**Date range:** [earliest] to [latest]
### 1. [Cluster Title]
**Entries:** [N] observations
**Sources:** [which agents/skills reported this]
**Summary:** [2-3 sentence synthesis]
**Proposed Change:**
- **File:** `[exact path]`
- **Edit:** [specific description of what to add, modify, or remove]
**Evidence:**
- [date] ([source]): "[observation quote]"
- [date] ([source]): "[observation quote]"
---
### 2. [Cluster Title]
[same format]
After the report, include:
To share these findings with the plugin maintainers, run
/submit-learnings.
Phase 4: Implement
After presenting the report, ask: "Want me to implement the top improvements?"
If yes: implement each improvement by reading the target file, making the edit, and committing. One commit per improvement: fix(qa): [description] — from learnings review. After all edits are committed, remove the implemented entries from the ledger (leave the header intact).
FAQ
What does the review-learnings skill do?
Synthesizes accumulated QA learnings from .qa-learnings/ledger.md into prioritized, actionable plugin improvements. Use when the user says "review learnings", "what have we learned", "improve the plugin", "learnings report", or "synthesize QA feedback".
How do I install review-learnings?
Run npx skills add https://github.com/neonwatty/qa-skills --skill review-learnings in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/review-learnings/ (personal) or .claude/skills/review-learnings/ (project).
Which AI agents can use review-learnings?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is review-learnings safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains review-learnings?
It is published by neonwatty in neonwatty/qa-skills. It has 51 recorded installs.
More from neonwatty/qa-skills
playwright-runner
neonwatty/qa-skills
Open the skill to read its SKILL.md instructions.
adversarial-audit
neonwatty/qa-skills
Audits SaaS and usage-based web apps for adversarial usage patterns — accidental, opportunistic, and deliberate. Use this when the user says "adversarial audit", "abuse case audit", "idiot-proof this app", "find usage exploits", "business logic audit", or "how could users break this". Explores the codebase to map the economic surface area (pricing tiers, usage limits, free trials, costly resources), then generates abuse cases where user behavior — intentional or not — could break assumptions, bypass limits, amplify costs, or corrupt state. Produces a prioritized markdown report with findings, code locations, and fix recommendations, then optionally verifies findings interactively in a browser.
mobile-workflow-to-playwright
neonwatty/qa-skills
Converts mobile workflow markdown into a self-contained Playwright test project with mobile viewports (Chromium + WebKit), authentication scaffolding, UX anti-pattern assertions, and CI workflow. Use when the user says "convert mobile workflows to playwright", "translate mobile workflows to CI", or "generate mobile playwright tests".
resilience-audit
neonwatty/qa-skills
Audits web apps for resilience against unexpected user behavior — accidental, edge-case, and chaotic. Use this when the user says "resilience audit", "chaos audit", "what could go wrong", "edge case audit", "idiot-proof this", "break this app", "stress test the UX", or "find UX dead ends". Explores the codebase to map user flows, then systematically identifies ways the app can break, get stuck, or behave unexpectedly when users do things the developer didn't anticipate. Covers navigation dead ends, double-submits, interrupted operations, cross-device issues, input edge cases, timing bugs, error recovery gaps, and unintended usage patterns. Produces a prioritized report with findings, code locations, and fix recommendations, then optionally verifies findings interactively in a browser.
use-profiles
neonwatty/qa-skills
Open the skill to read its SKILL.md instructions.
multi-user-workflow-generator
neonwatty/qa-skills
Generates multi-user workflow documentation by interviewing the user about personas, exploring the codebase for multi-user patterns, then walking through the live app with per-persona Playwright CLI named sessions to co-author interleaved, persona-tagged workflows. Use when the user says "generate multi-user workflows", "create multi-user workflows", or "generate concurrent user workflows". Produces persona-tagged workflow markdown that feeds into the multi-user converter and Playwright runner.
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.