wolfssl-issue-review

Automates end-to-end wolfSSL GitHub issue reviews, generating patches, reproducers, and BEFORE/AFTER test harnesses per issue.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/cpsource/wolfssl-issue-review --skill wolfssl-issue-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wolfssl-issue-review
Source: https://github.com/cpsource/wolfssl-issue-review/tree/main
Command: npx skills add https://github.com/cpsource/wolfssl-issue-review --skill wolfssl-issue-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

The Skill enables a one-shot workflow to review wolfSSL GitHub issues end-to-end, producing per-issue artefacts (README-issue-N.md, issue-N.patch, issue-N-test.c, test.sh) and ready-to-post content, all from a single prompt.

Core Features & Use Cases

  • Generates a complete per-issue review package under wolfssl-issues/issue-N/, including a 10-section README, a patch, a C reproducer, and a BEFORE/AFTER test harness, with acceptance gates.
  • Automates Phase 1-14 workflow: tree prep, issue fetch, upstream scan, root-cause read, patch generation, reproducer creation, testing, and optional GitHub reply drafting.
  • Uses the wolfSSL working tree and a sibling wolfssl-issues sub-repo to store artefacts; can be installed into Claude Code environment for reuse.

Quick Start

Invoke the action with review issue 10287 to generate the full artefact set for that wolfSSL issue.

Frequently Asked Questions about wolfssl-issue-review

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

FAQPage Schema
How do I automate wolfSSL issue review end-to-end from a GitHub bug report?

wolfSSL issue review can be fully automated by invoking a single prompt that collects issue data, runs upstream scans, and generates per-issue artefacts. It produces a patch, C reproducer, and test harness directly in your local clone.

What artefacts are generated when reproducing a wolfSSL bug?

Reproducing a wolfSSL bug generates a complete package containing a 10-section README, a patch file, a C reproducer, and a test script. These artefacts are stored under a dedicated wolfssl-issues sub-repo for tracking.

Do I need a local wolfSSL clone to run automated patch generation and testing?

Yes, automated patch generation requires access to a local wolfSSL working tree and a sibling wolfssl-issues sub-repo. You also need the specified Claude Code tools installed in your environment to execute the workflow.

Can I draft a GitHub reply automatically after creating a wolfSSL patch and reproducer?

Yes, the workflow includes an optional phase to draft ready-to-post GitHub replies after creating the wolfSSL patch and reproducer. This happens after the BEFORE/AFTER test harness successfully validates the generated artefacts.

What does the BEFORE/AFTER test harness do for wolfSSL issue patches?

The BEFORE/AFTER test harness validates the generated wolfSSL patch by running the C reproducer against the unpatched and patched code. This verifies the fix resolves the issue without introducing regressions before posting.