diagnostic-integrity

Enforce diagnostic integrity protocols for Pact/Kadena smart-contract tests.

1|1|Updated Jun 9, 2026
One-click install
npx skills add https://github.com/Pact-Community-Organization/github-marketplace --skill diagnostic-integrity
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diagnostic-integrity
Source: https://github.com/Pact-Community-Organization/github-marketplace/tree/main/skills/diagnostic-integrity
Command: npx skills add https://github.com/Pact-Community-Organization/github-marketplace --skill diagnostic-integrity

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

False positives in smart-contract diagnostics can derail debugging and waste time; this skill enforces truth-telling, failure protocols, and a formal self-audit before reporting results.

Core Features & Use Cases

  • Self-audit workflow before every diagnostic report to ensure evidence integrity.
  • Structured failure handling (STOP, ANALYZE, CLASSIFY, PROPOSE) to guide remediation and prevent rash fixes.
  • Pattern guidance for eight false-positive patterns to prevent silent passes.

Quick Start

Run a full self-audit checklist before generating any diagnostic report.

Frequently Asked Questions about diagnostic-integrity

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

FAQPage Schema
How do I prevent false positives in smart contract test suites?

To prevent false positives in smart contract test suites, enforce a self-audit workflow before generating diagnostic reports. This process identifies silent passes and ensures truthful test results by validating evidence integrity.

What is the deterministic failure workflow for Pact smart contract diagnostics?

The deterministic failure workflow for Pact diagnostics is STOP, ANALYZE, CLASSIFY, and PROPOSE. This structured sequence guides remediation and prevents rash fixes by systematically handling smart contract test failures.

How do I handle false positive patterns in Kadena smart contract tests?

Handling false positive patterns in Kadena smart contract tests requires explicit guidance for eight specific silent pass scenarios. The self-audit checklist enforces post-run verification to prevent inaccurate diagnostic reports.

When do I need a self-audit checklist for smart contract CI pipelines?

You need a self-audit checklist for smart contract CI pipelines when running post-run verification to ensure evidence integrity. It enforces diagnostic truth-telling and classifies failures before reporting results.

Does this diagnostic integrity workflow support Pact and Kadena environments?

Yes, this diagnostic integrity workflow explicitly supports Pact and Kadena environments. It applies self-audit triggers and failure classification protocols across test suites, CI pipelines, and audit reports.

What are the limitations of automated smart contract diagnostic reports?

Automated smart contract diagnostic reports are limited by silent passes and unclassified test failures. Without enforcing a formal self-audit checklist and deterministic failure workflow, they risk generating inaccurate false positives.