From scopy_dev_plugin
Generates 'What's New' HTML page for Scopy plugin at specified version, discovers features from docs/state/manifest, drafts for approval, then creates file in resources/whatsnew/<version>/.
npx claudepluginhub analogdevicesinc/scopy --plugin scopy_dev_plugin# /create-whatsnew — Generate What's New HTML page You are creating a "What's New" HTML page for a Scopy plugin release. **Arguments:** `$ARGUMENTS` (Format: `<plugin> <version>` — e.g., `ad9371 V2.2.0`) ## Step 0: Parse arguments and load context Parse `$ARGUMENTS` to extract: - **Plugin name** — first word (e.g., `ad9371`) - **Version** — second word (e.g., `V2.2.0`) Use the Read tool to check if a port state file exists: - Path: `tasks/<plugin>-port-state.md` (substitute the parsed plugin name) - If the file does not exist, note "No state file — will discover from plugin docs." and ...
/release-docsBuilds and updates the static HTML documentation site by inventorying plugin agents, commands, skills, and MCP servers. Supports optional --dry-run preview.
/product-reportGenerates offline-readable HTML planning report from conversation's product planning content, dynamically rendering completed stages with sticky TOC and interactive cards.
/docs-updateSyncs documentation across README files and wiki articles by locating wiki repo, analyzing main repo changes, interactively confirming updates, and committing to both.
/generate-visual-planGenerates a self-contained HTML visual implementation plan for a feature, with state machines, code snippets, edge cases, and specs.
/load-docsLoad plugin documentation on-demand with intelligent link extraction and parallel WebFetch for any plugin in the marketplace
/previewLaunches interactive preview for HTML document editing: starts local HTTP server, sets up control panel, opens wrapper in Playwright browser.
Share bugs, ideas, or general feedback.
You are creating a "What's New" HTML page for a Scopy plugin release.
Arguments: $ARGUMENTS
(Format: <plugin> <version> — e.g., ad9371 V2.2.0)
Parse $ARGUMENTS to extract:
ad9371)V2.2.0)Use the Read tool to check if a port state file exists:
tasks/<plugin>-port-state.md (substitute the parsed plugin name)Use the Glob tool to check if the version folder exists:
scopy/resources/whatsnew/<version>/ (substitute the parsed version)Feature inventory (in priority order):
scopy/docs/plugins/<plugin>/index.rst and <plugin>.rst — feature list, device support, key parametersdisplay_name, description, deviceRead the reference prompt for HTML patterns and validation:
scopy/tools/prompts/scopy_whatsnew_agent.md
Study these reference HTML files before writing:
scopy/resources/whatsnew/V2.2.0/adrv9002_plugin.html — comprehensive example (RF transceiver)scopy/resources/whatsnew/V2.2.0/imuanalyzer_plugin.html — simpler examplescopy/resources/whatsnew/V2.2.0/rfpowermeter.html — another styleStudy the QRC file for how to add entries:
scopy/resources/whatsnew/whatsnew.qrcPresent the HTML content draft:
<h1><Device Display Name> Plugin</h1><h2>Key Features</h2> with <ul>/<li> — one item per major section<h2>How to Use</h2> with numbered <ol>/<li> steps<a href="https://analogdevicesinc.github.io/scopy/plugins/<plugin>/<plugin>.html"><file>VERSION/<plugin>_plugin.html</file>Wait for user approval before writing any files.
If scopy/resources/whatsnew/<version>/ does not exist, create it.
Create scopy/resources/whatsnew/<version>/<plugin>_plugin.html
HTML template:
<h1><Device Display Name> Plugin</h1>
<p>Scopy now offers dedicated support for the <Device Name>.</p>
<p>The new <b><Tool Display Name> Tool</b> enables you to integrate and control <Device>-based devices within Scopy. <One sentence describing the key capability.></p>
<h2>Key Features</h2>
<ul>
<li><b>Section Name:</b> Brief description of what this section controls</li>
</ul>
<h2>How to Use</h2>
<ol>
<li>Connect your <Device> device to your computer.</li>
<li>Ensure the <Device> IIO drivers are properly installed.</li>
<li>Open Scopy and select the <b><Tool Name></b> tool from the available instruments.</li>
</ol>
<p>For more detailed information, please visit the <a href="https://analogdevicesinc.github.io/scopy/plugins/<plugin>/<plugin>.html" target="_blank">official documentation</a>.</p>
Rules for HTML content:
<b> for bold emphasis — no CSS, no inline styles<h1> for the title, <h2> for sections — no <h3> or deeper<ul>/<li> for feature lists, <ol>/<li> for how-to steps<!DOCTYPE>, <html>, <head>, or <body> tags — this is an HTML fragmentEdit scopy/resources/whatsnew/whatsnew.qrc to add the new <file> entry in alphabetical order within the version group.
<html>/<head>/<body> tags)<h1> and <h2> heading levels used<file> entry added to whatsnew.qrc in the correct version groupmanifest.json.cmakein display_name field## Status
- Phase: WHATSNEW_COMPLETE
<h3> or deeper heading levelsanalogdevicesinc.github.io/scopy — do not guess other URLs