dogfood-verification

Verify running ObjectStack applications through browser interactions and server responses.

22|6|Updated Jan 18, 2026
One-click install
npx skills add https://github.com/objectstack-ai/objectstack --skill dogfood-verification
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dogfood-verification
Source: https://github.com/objectstack-ai/objectstack/tree/main/.claude/skills/dogfood-verification
Command: npx skills add https://github.com/objectstack-ai/objectstack --skill dogfood-verification

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill catches runtime, UI, configuration, and permission problems that static checks and unit tests can miss by validating a real ObjectStack application in an isolated environment.

Core Features & Use Cases

  • Environment Isolation: Separates the development server, database, browser session, and potential pull-request worktree to avoid interference from parallel sessions.
  • Authoritative Verification: Combines screenshots, browser interactions, API responses, and application metadata to distinguish real defects from hydration or stale-build artifacts.
  • Safe Debugging and Shipping: Guides package rebuilding, server restarts, dependency-gate testing, and clean pull-request preparation with changesets.
  • Use Case: Use this Skill to boot a showcase or CRM app, verify Setup or Studio behavior as an administrator or user, investigate a missing feature, and confirm the fix in the running application before shipping.

Quick Start

Use the dogfood verification skill to boot an isolated ObjectStack app, verify the changed workflow in the browser and through its API, and report only findings confirmed by visual or authoritative evidence.

Frequently Asked Questions about dogfood-verification

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

FAQPage Schema
How do I verify a running application in the browser to catch runtime bugs missed by static checks?

Browser verification catches runtime and UI bugs by combining screenshots, interactions, and API responses to distinguish real defects from stale-build artifacts in an isolated environment. This disciplined approach confirms visual behavior and authoritative server responses before shipping.

What is the best way to isolate a development server and database for safe dogfooding?

Environment isolation separates the development server, database, browser session, and pull-request worktree to avoid interference from parallel sessions. This isolated setup ensures safe dogfooding by preventing cross-session data collisions during runtime testing.

How do I test permissions and dependency gates in a running CRM app?

Testing permissions and dependency gates requires booting the CRM app in an isolated environment and verifying Setup or Studio workflows as an administrator. Visual confirmation and API validation ensure permission rules and dependency gates function correctly at runtime.

Why does my application show missing features or hydration errors after a package rebuild?

Hydration errors and missing features often stem from stale builds or incorrect dist awareness rather than true defects. Authoritative verification distinguishes these artifacts from real bugs by validating application metadata and confirming visual state against API responses.

Can I use visual testing to confirm a fix before preparing a pull request?

Visual testing confirms fixes by verifying the changed workflow in the browser and through its API before shipping. This process guides package rebuilding, server restarts, and clean pull-request preparation with changesets to ensure safe debugging.

When do I need isolated ports for runtime testing of a showcase application?

Isolated ports are required when booting a showcase application for runtime testing to avoid network conflicts with parallel sessions. This separation ensures browser verification and API validation operate safely without interference from other active development environments.