gormes-install

Validate Gormes install.sh and install.ps1 pipelines in a sandboxed environment.

9|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/TrebuchetDynamics/gormes-agent --skill gormes-install
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gormes-install
Source: https://github.com/TrebuchetDynamics/gormes-agent/tree/main/development-skills/gormes-install
Command: npx skills add https://github.com/TrebuchetDynamics/gormes-agent --skill gormes-install

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps operators verify and validate Gormes install and setup paths across fresh-user, development, and production flows, surfacing issues before they impact end users.

Core Features & Use Cases

  • Sandbox-based install validation for install.sh and install.ps1, including pre-state and post-state diffs, and autonomous regression detection.
  • Dry-run planning and verbose logging to confirm isolation boundaries and gateway freshness.
  • Comprehensive coverage of fresh installs, local checkout installations, and guided remediation through known-issues tracking.

Quick Start

Run the sandbox plan with dry-run to preview changes before performing a full install

Frequently Asked Questions about gormes-install

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

FAQPage Schema
How do I validate install.sh and install.ps1 scripts in a sandboxed environment?

Sandbox-based install validation automates testing for install.sh and install.ps1 by capturing pre-state and post-state diffs to detect regressions. It enforces isolation boundaries and logs issues to a known-issues registry for guided remediation.

What is pre-state and post-state diff analysis for installation testing?

Pre-state and post-state diff analysis captures the baseline system state before an install and compares it against the state afterward. This regression detection surfaces unauthorized or unexpected changes made by install scripts.

How do I dry-run an install pipeline to preview system changes?

Dry-run planning executes the sandbox plan to preview changes without performing a full install. It validates isolation boundaries and gateway freshness using verbose logging before applying actual modifications.

Does this sandbox validation cover fresh-user installs and local development checkouts?

Yes, the sandbox validation provides comprehensive coverage for fresh-user installs, local checkout installations, and production flows. It verifies setup paths across these environments to surface issues before impacting users.

Why do I need sandbox boundaries during system installation testing?

Sandbox boundaries are needed to enforce isolation and prevent install scripts from making unauthorized system changes. Capturing baseline state within these boundaries ensures accurate regression verification and safe remediation tracking.