agm-validate-change

Selects and runs the smallest validation set for Antigravity Manager worktree changes.

2.1k|262|Updated Nov 29, 2025
One-click install
npx skills add https://github.com/Draculabo/AntigravityManager --skill agm-validate-change
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agm-validate-change
Source: https://github.com/Draculabo/AntigravityManager/tree/main/.agents/skills/agm-validate-change
Command: npx skills add https://github.com/Draculabo/AntigravityManager --skill agm-validate-change

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After modifying the Antigravity Manager repository, developers often either run the entire test suite wastefully or skip validation entirely. This Skill maps each change to the minimum reliable evidence needed, so validation is proportionate to what the diff can actually affect.

Core Features & Use Cases

  • Change Classification: Categorizes changed paths as documentation, renderer UI, routing, IPC/preload, Electron main lifecycle, persistence/security, proxy protocol, build/update, or shared contract.
  • Evidence Selection: Chooses targeted unit tests, type-check, agent-contract checks, or focused Playwright runs based on the affected surfaces instead of defaulting to the full suite.
  • Failure Handling: Requires diagnosing failing checks before widening scope and forbids weakening assertions or blaming the environment without evidence.
  • Use Case: After editing an IPC contract between the Electron main process and the React renderer, run the owning integration test plus npm run type-check rather than the full rehearsal, then report residual risk.

Quick Start

Ask the assistant to validate the current worktree changes in the Antigravity Manager repository using the smallest appropriate set of checks.

Frequently Asked Questions about agm-validate-change

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

FAQPage Schema
How do I validate changes in an Electron app without running the full test suite?

Classify each changed path by affected layer, then run only the owning unit or integration test plus type-check for shared contracts. Reserve the full rehearsal for repository-wide changes or explicit requests.

What tests should I run after changing IPC or preload code in Electron?

Run the owning integration test for the IPC contract and add npm run type-check, since IPC changes cross module boundaries and shared types. Mock-only tests are not sufficient proof of native Electron behavior.

When should I use Playwright tests for Electron changes?

Use focused Playwright evidence only for user flows that require the packaged Electron boundary. Purely local component changes do not need end-to-end Playwright runs.

What should I do when a validation check fails?

Diagnose the specific failure before widening scope. Do not skip the check, weaken assertions, or blame the environment without concrete evidence; stop only if fixing exceeds the requested change's authority.

Can mock-only tests prove native Electron or keyring behavior?

No. Mock-only tests cannot prove native Electron, keyring, installer, or live-provider behavior. Environment-dependent paths require packaging, keyring, updater, or live-provider evidence when the diff can affect them.