debug-pact

Debug Pact 5 smart contracts and diagnose deployment and runtime errors.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pact 5 smart contracts often fail during development or on devnet, and root causes can be hard to identify without structured debugging tools.

Core Features & Use Cases

  • REPL debugging to inspect intermediate values and enforce expected behavior.
  • Devnet error diagnosis and transaction failure analysis to pinpoint root causes.
  • Gas profiling to benchmark and optimize contract execution.

Quick Start

Run a Pact REPL session with the failing contract and reproduce the error to collect actionable diagnostics.

Frequently Asked Questions about debug-pact

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

FAQPage Schema
How do I debug a Pact smart contract that fails on devnet?

To debug a failing Pact smart contract on devnet, run a Pact REPL session with the failing contract to reproduce the error and capture transaction results for diagnosis. This isolates runtime errors and deployment failures.

What is gas profiling for Pact contracts and when do I need it?

Gas profiling for Pact contracts measures execution cost across contract operations to benchmark and optimize gas usage. You need it when evaluating transaction efficiency or reducing execution overhead during development.

Can I trace intermediate values in a Pact REPL session to find execution errors?

Yes, you can trace intermediate values in a Pact REPL session to inspect execution state and enforce expected behavior. Deterministic tracing steps capture values during execution to pinpoint where contract logic fails.

What is the best way to diagnose transaction failure analysis for Pact 5 contracts?

The best way to diagnose Pact 5 transaction failures is reproducing the error in a REPL environment to collect actionable diagnostics. Structured error diagnosis captures transaction results to identify root causes effectively.

Do I need a devnet environment to troubleshoot Pact smart contract deployment errors?

While devnet error diagnosis captures deployment failures, you can reproduce and debug many Pact contract errors directly in a local REPL session. Devnet is specifically needed for diagnosing network-dependent transaction failures.