review-learnings

Included with Lifetime

$97 forever

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".

Code Review

What this skill does


# 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:

```markdown
## 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).

Files: 1

Size: 2.5 KB

Complexity: 12/100

Category: Code Review

Source: https://github.com/neonwatty/qa-skills/tree/main/skills/review-learnings

Related in Code Review

gstack

Included

Fast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)

Code Reviewscriptsfeatured

startup-due-diligence

Included

Legal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.

Code Reviewscripts

interview-master

Included

This skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.

Code Reviewscripts

fix-issue

Included

Fixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.

Code Reviewscripts

sf-apex

Included

Generates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.

Code Reviewscripts

swift-development

Included

Comprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.

Code Reviewscripts