verify

Validate @inflexa-ai/harness package changes against a containerized Postgres database.

29|3|Updated Jun 11, 2026
One-click install
npx skills add https://github.com/inflexa-ai/inflexa --skill verify-inflexa-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/inflexa-ai/inflexa/tree/main/harness/.claude/skills/verify
Command: npx skills add https://github.com/inflexa-ai/inflexa --skill verify-inflexa-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires neverthrow, zod.

What problem does it solve?

This skill addresses the difficulty of testing library-level changes in the @inflexa-ai/harness package, which is typically consumed by a CLI, by providing a sandbox environment to verify code changes before they are integrated.

Core Features & Use Cases

  • Package Boundary Testing: Build and link the harness library into a scratch consumer to observe uncommitted changes.
  • Integration Validation: Drive runAgent, tools, and gateways against a real Postgres instance using podman.
  • Use Case: When modifying core harness logic, use this skill to ensure that the new code correctly interacts with the database and agent state without needing to fully deploy the CLI.

Quick Start

Execute the verify skill to build the harness package and run the integration tests against a local Postgres container.

Frequently Asked Questions about verify

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

FAQPage Schema
How do I test uncommitted library changes against a consumer environment?

Package boundary testing builds and links your library into a scratch consumer environment to observe uncommitted changes before integration. This simulates a real consumer setup to validate code modifications safely.

How does integration testing with a containerized Postgres database work?

Integration testing validates agents, tools, and gateways by driving them against a real Postgres instance using podman. This verifies core logic correctly interacts with the database and agent state within a sandboxed environment.

Do I need podman and Node.js to run package-level verification scripts?

Yes, you need both a local podman environment and a Node.js runtime to execute package-level verification scripts. These dependencies are required to build the harness and run integration tests against the local Postgres container.

Can I validate agent state changes without fully deploying the CLI?

Yes, you can validate agent state changes without a full CLI deployment by using a sandbox environment. This simulates the consumer environment to verify database interactions and core harness logic directly.

What is the best way to verify core harness logic before integrating code changes?

The best way to verify core harness logic is executing a verification skill that builds the harness package and runs integration tests against a local containerized Postgres database. This ensures new code correctly interacts with required services before integration.