What's New (2026.09.08)

This release reorganizes the Polyspace Agentic Toolkit around one skill group per Polyspace product, adds full support for Polyspace Bug Finder and Polyspace Code Prover, and lets setup install only the skills for the products you actually have. The skill catalog grows from 11 to 19 skills across six groups.

New Skill Groups

Polyspace Core (polyspace-core) — Always installed. Resolves the Polyspace installation root, configures build options, and provides documentation entry points shared by every workflow.
Polyspace Static Core (polyspace-static-core) — Shared static-analysis workflow installed whenever any static-analysis product (Polyspace as You Code, Bug Finder, or Code Prover) is present. Review, fix, and justify findings; configure checkers; and look up checker and option documentation.
Polyspace Bug Finder (polyspace-bug-finder) — Analyze defects and coding-standard compliance across several files or a whole component.
Polyspace Code Prover (polyspace-code-prover) — Prove the absence of run-time errors, review red/orange/green/gray checks, and triage orange (unproven) checks.

New Skills in Existing Skill Groups

Polyspace Bug Finder — run-polyspace-bug-finder-analysis to run Bug Finder across several files or a whole component.
Polyspace Code Prover — run-polyspace-code-prover-analysis to run Code Prover on C/C++ code, review-polyspace-code-prover-results to read and prioritize checks, and triage-orange-checks to decide what to do about unproven checks.
Polyspace Core — resolve-polyspace-root to locate the installation root for command-line fallbacks.
Polyspace Static Core — polyspace-review-findings as a dedicated skill for reading, explaining, and prioritizing findings, and polyspace-justify-in-database for recording a review status and rationale in the results database and carrying it across re-runs.
Polyspace Test — run-polyspace-test-xunit-tests to build and run PSTUnit tests, optionally computing code coverage. If a Make/CMake-based build system is in place to build sources, the skill produces a copy of the build files (makefile, CMakelists) to incorporate tests. The skill accounts for common issues such as missing test registration.

Improved Skills

run-polyspace-as-you-code-analysis — focused on file-level analysis of the file you are editing, now that shared review, fix, justify, checker, and documentation skills live in polyspace-static-core.
generate-polyspace-test-xunit-tests — expanded PSTUnit test-authoring guidance with C and C++ API references.

Compatibility Considerations

This release splits the single polyspace-as-you-code group into shared groups (polyspace-core, polyspace-static-core) and product-specific groups, and renames skills to a consistent polyspace-* convention. To update your installed skills, re-run setup ("Set up the Polyspace Agentic Toolkit").

Skills that moved and/or were renamed:

Previously (in `polyspace-as-you-code`)	Now
`run-analysis`	`polyspace-as-you-code/run-polyspace-as-you-code-analysis`
`configure-build-options`	`polyspace-core/polyspace-configure-build-options`
`documentation-entry-points`	`polyspace-core/polyspace-documentation-entry-points`
`configure-checkers`	`polyspace-static-core/polyspace-configure-checkers`
`find-checker-documentation`	`polyspace-static-core/polyspace-find-checker-documentation`
`find-option-documentation`	`polyspace-static-core/polyspace-find-option-documentation`
`fix-findings`	`polyspace-static-core/polyspace-fix-findings`
`query-justification-catalog`	`polyspace-static-core/polyspace-query-justification-catalog`

The justify-findings skill has been split into two focused skills:

Removed	Replaced by
`polyspace-as-you-code/justify-findings`	`polyspace-static-core/polyspace-justify-in-code` (in-source annotation comment) and `polyspace-static-core/polyspace-justify-in-database` (review status/rationale in the results database)

The Polyspace Test authoring skill was renamed:

Previously	Now
`polyspace-test/generate-xunit-tests`	`polyspace-test/generate-polyspace-test-xunit-tests`

Agentic Toolkit Installer

Selective installation. Setup now detects which Polyspace products you have installed and installs only the matching skill groups, after you confirm the set. polyspace-core is always installed, and polyspace-static-core is installed whenever any static-analysis product (Polyspace as You Code, Bug Finder, or Code Prover) is present. polyspace-test drives dynamic testing and does not require polyspace-static-core. Fewer loaded skills means agents trigger the right skill more reliably. To add or remove products later, re-run setup and adjust the confirmed set.
Targeted skill registration. scripts/install-global-skills.sh now accepts an optional list of skill-group names, so symlink-based agents can register only the selected groups (no arguments install everything, as before).
Automatic dependency for Claude Code. Each product plugin (polyspace-as-you-code, polyspace-bug-finder, polyspace-code-prover) declares polyspace-static-core as a dependency, so installing any product plugin pulls in the shared static-analysis skills automatically.

Other Changes

Expanded Model Context Protocol (MCP) tool surface. The MCP Tools documentation now covers Bug Finder and Code Prover analysis (run_polyspace_bug_finder, run_polyspace_code_prover), Code Prover–specific inspection (get_code_prover_assumptions, get_concurrency_model, get_orange_sources, get_static_ranges), and additional results-exploration tools, including get_dead_code_blocks.
Documentation. The README documents the per-product skill groups, the selective-installation model, and a product-to-group mapping table.

Navigation Menu

Repository navigation

Release 2026.09.08

Choose a tag to compare

Sorry, something went wrong.