June 1, 2026
Kinetic Gain Suite PR Gate
Version updated for https://github.com/mizcausevic-dev/kg-suite-pr-gate-action to version v0.1.0.
This action is used across all versions by ? repositories. Action Type This is a Node action using Node version 20.
Go to the GitHub Marketplace to find the latest changes.
Action Summary The kg-suite-pr-gate-action is a GitHub Action designed to automate the review of JSON document changes in pull requests for repositories using the Kinetic Gain Suite. It identifies protocol-specific changes across five Suite protocols, performs diffs using appropriate tools, and consolidates the results into a single PR comment, highlighting breaking changes. This action simplifies PR review workflows by replacing the need for multiple individual steps with a unified, efficient solution.
June 1, 2026
Kinetic Gain Suite Spec-Version Tracker
Version updated for https://github.com/mizcausevic-dev/kg-suite-spec-version-tracker-action to version v0.1.0.
This action is used across all versions by ? repositories. Action Type This is a Node action using Node version 20.
Go to the GitHub Marketplace to find the latest changes.
Action Summary The kg-suite-spec-version-tracker-action is a GitHub Action designed to analyze Kinetic Gain Suite JSON documents in a specified directory, identify their protocol and specification versions, and detect version drift within or across protocols. It automates version governance by flagging and failing builds when multiple spec versions of the same protocol are detected, helping teams maintain consistency and avoid “silent migration debt.” This action provides cross-protocol governance, version drift detection, and reporting capabilities, ensuring alignment across teams using the Kinetic Gain Suite.
June 1, 2026
MCP Tool Card Diff
Version updated for https://github.com/mizcausevic-dev/mcp-tool-card-diff-action to version v0.1.0.
This action is used across all versions by ? repositories. Action Type This is a Node action using Node version 20.
Go to the GitHub Marketplace to find the latest changes.
Action Summary The mcp-tool-card-diff-action GitHub Action automates the validation of changes to MCP Tool Card JSON files in pull requests by comparing the modified file against its previous version. It generates and posts a structured diff as a PR comment, identifying breaking changes and optionally failing the build if such changes are detected. This action streamlines the review process, enforces compliance with change policies, and integrates with related tools for managing MCP Tool Cards.
June 1, 2026
MCP Tool Card Fleet Summary
Version updated for https://github.com/mizcausevic-dev/mcp-tool-card-fleet-summary-action to version v0.1.0.
This action is used across all versions by ? repositories. Action Type This is a Node action using Node version 20.
Go to the GitHub Marketplace to find the latest changes.
Action Summary The mcp-tool-card-fleet-summary-action is a GitHub Action designed to analyze a directory of MCP Tool Card documents, identify governance gaps, and assess potential risks based on predefined rules. It automates the generation of a Markdown summary that is posted as a pull request comment and can fail builds if high-severity issues are detected. This action provides key capabilities for ensuring compliance and governance by flagging issues like missing approvals, audit logs, or safety measures in a fleet of tools.
June 1, 2026
MCP Tool Card README Generator
Version updated for https://github.com/mizcausevic-dev/mcp-tool-card-readme-generator-action to version v0.1.0.
This action is used across all versions by ? repositories. Action Type This is a Node action using Node version 20.
Go to the GitHub Marketplace to find the latest changes.
Action Summary The mcp-tool-card-readme-generator-action is a GitHub Action designed to automate the generation of human-readable Markdown README files from MCP Tool Card JSON files. It ensures documentation stays synchronized with the JSON by either writing the generated README to a specified file path or posting it as a pull request comment. This action streamlines the process of maintaining up-to-date, consistent documentation for MCP Tool Cards, reducing manual effort and improving workflow efficiency.
June 1, 2026
OTel GenAI Diff
Version updated for https://github.com/mizcausevic-dev/otel-genai-diff-action to version v0.1.0.
This action is used across all versions by ? repositories. Action Type This is a Node action using Node version 20.
Go to the GitHub Marketplace to find the latest changes.
Action Summary The otel-genai-diff-action GitHub Action automates the validation of changes in OTel GenAI rollup reports within pull requests by calculating structured diffs between the current and previous report versions. It identifies and flags significant cost or token usage increases (with a default 10% threshold), posts the analysis as a PR comment, and optionally fails the build for breaking changes. This action streamlines the review process by ensuring cost efficiency and consistency across AI tooling updates.
June 1, 2026
OTel GenAI Fleet Summary
Version updated for https://github.com/mizcausevic-dev/otel-genai-fleet-summary-action to version v0.1.0.
This action is used across all versions by ? repositories. Action Type This is a Node action using Node version 20.
Go to the GitHub Marketplace to find the latest changes.
Action Summary The otel-genai-fleet-summary-action GitHub Action automates the analysis of OpenTelemetry GenAI OTLP span exports, identifying governance issues such as unauthorized model usage, missing attributes, and high error rates. It posts a Markdown summary of findings as a pull request comment and can fail builds when high-severity issues are detected, ensuring compliance and improving oversight of large language model (LLM) trace data across fleets. Key capabilities include error rate monitoring, model validation, and integration with other governance tools in the Kinetic Gain Suite.
June 1, 2026
Procurement Pulse — Self-Score
Version updated for https://github.com/mizcausevic-dev/procurement-pulse-action to version v0.1.0.
This action is used across all versions by ? repositories. Action Type This is a Node action using Node version 20.
Go to the GitHub Marketplace to find the latest changes.
Action Summary This GitHub Action evaluates a domain’s compliance with the Kinetic Gain Protocol Suite by probing its /.well-known/ paths and calculating a disclosure score (0–100) and tier ranking. It automates tasks such as self-scoring on pull requests, gating releases based on compliance thresholds, publishing score badges, and generating timestamped JSON receipts of the evaluation. This action helps organizations monitor and maintain protocol adherence, prevent regressions, and streamline compliance reporting.
June 1, 2026
Prompt Provenance Diff
Version updated for https://github.com/mizcausevic-dev/prompt-provenance-diff-action to version v0.1.0.
This action is used across all versions by ? repositories. Action Type This is a Node action using Node version 20.
Go to the GitHub Marketplace to find the latest changes.
Action Summary The Prompt Provenance Diff Action is a GitHub Action designed to automate the validation of changes to a prompt-provenance JSON document in pull requests. It detects and flags breaking changes, such as alterations to prompt hashes, approval states, or document lineage, posts a structured diff as a PR comment, and can fail the build if necessary. This action helps ensure document integrity and compliance with predefined provenance protocols, streamlining the review process for prompt-related changes.
June 1, 2026
Prompt Provenance Fleet Summary
Version updated for https://github.com/mizcausevic-dev/prompt-provenance-fleet-summary-action to version v0.1.0.
This action is used across all versions by ? repositories. Action Type This is a Node action using Node version 20.
Go to the GitHub Marketplace to find the latest changes.
Action Summary The prompt-provenance-fleet-summary-action is a GitHub Action designed to analyze a directory of prompt-provenance documents, identify governance gaps, and count prompts by their approval states. It automates the generation of a Markdown summary, posts it as a pull request comment, and optionally fails the build if high-severity issues are detected. This action streamlines governance and compliance checks for prompt-provenance documentation, ensuring quality and accountability in prompt management workflows.