Skip to content
cccskills
FreePublished on GitHub

review-findings

Address issues identified in a QA code review by investigating causes, fixing critical problems first, and updating tests. The skill prepares a fix report that records changes and explains any deferred warnings for re-verification.

OriginalShow the original description

Addresses and fixes findings from a QA code review. Reads the review report, fixes critical and warning issues, and prepares for re-verification. Delegates to the Forja (Dev) agent.

See how to install

Good for

  • Fixing critical issues after a code review
  • Updating tests alongside review fixes
  • Documenting reasons for deferred warnings
  • Preparing a fix report for QA re-verification

Files included (1)

  • SKILL.md1.6 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Review Findings

Addresses and fixes QA findings using the Forja (Dev) agent.

When to Use This Skill

  • After receiving a code review from Centinela (QA)
  • When a review report has findings that need to be addressed
  • Fixing critical and warning issues before re-verification

What This Skill Does

  1. Runs the SIGN IN checklist
  2. Reads the review report and understands each finding's root cause
  3. Plans fix order: Critical first, then Warnings
  4. Implements fixes with updated tests for each finding
  5. Scans for dead code after all fixes
  6. Runs Implementation Complete and Pre-Delivery checklists (TIME OUT)
  7. Verifies every Critical finding addressed, every Warning addressed or deferred with justification
  8. Prepares a fix report for QA re-verification

How to Use

Basic Usage

/review-findings

With Specific Review

/review-findings docs/reviews/user-auth-review.md

Example

User: /review-findings docs/reviews/webhook-system-review.md

Output:

  • All Critical findings fixed with tests
  • All Warning findings fixed or explicitly deferred with justification
  • Fix report documenting what was changed and why
  • Ready for QA re-verification

Tips

  • If no review is specified, the most recent review in docs/reviews/ is used
  • The agent understands root causes before writing any fix
  • Conflicting fixes are identified and planned around during the pre-fix phase

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Handle ActiveCampaign contact and marketing tasks through Rube MCP, a connection for agent tools. Find or create contacts, manage tags and subscriptions, enroll contacts in existing automated workflows, and create follow-up tasks.

  • Finding or registering contacts
  • Adding or removing contact tags
  • Subscribing contacts to lists or unsubscribing them
davepoon/buildwithclaude3.7KUpdated Oct 20, 2026

Research competitors’ live Meta and Google ads to identify opening hooks, offers, calls to action, and landing pages. Receive a sourced creative brief and up to three test ideas adapted to your product.

  • Find angles for new ad copy
  • Plan creative tests using competitor ads
  • Choose a landing page message
davepoon/buildwithclaude3.7KUpdated Oct 20, 2026

agent-analytics

FreeSummary

Add website or app tracking, then use command-line tools to review traffic, signups, drop-off, and returning users across projects. Run A/B tests, which compare alternative headlines or buttons, and inspect results to guide changes.

  • Adding page-view and key-action tracking
  • Reviewing traffic and referral sources across projects
  • Finding where visitors drop out before signup or purchase
davepoon/buildwithclaude3.7KUpdated Oct 20, 2026

Establish rules for when an AI agent should recall past context and save lasting decisions, corrections, preferences, and failures. Works with Markdown files or memory services, preserving decision history and surfacing conflicting records.

  • Carry project conventions into the next session
  • Save user corrections and lasting preferences
  • Record failed approaches and their causes
davepoon/buildwithclaude3.7KUpdated Oct 20, 2026

Audit local AI coding-agent sessions with agenttrace to identify spending, token use, tool failures, and operational problems. Produce readable or structured reports and define pass-or-fail thresholds for automated continuous integration checks.

  • Investigating session costs and token waste
  • Finding repeated tool failures and retries
  • Exporting session reports as Markdown or JSON
davepoon/buildwithclaude3.7KUpdated Oct 20, 2026

Audit saved agent sessions for access to private files and evidence that secret values entered an agent's context. Get findings without displaying secrets, identify keys needing rotation, and inspect Claude Code or Codex sessions in a local report.

  • Check whether an agent accessed .env files
  • Identify keys that may need rotation
  • Audit private-file access by subagents
davepoon/buildwithclaude3.7KUpdated Oct 20, 2026

See all skills by davepoon

Report a problem with this skill