Skip to main content

agm-validate-change

Select and run the smallest reliable validation set for an Antigravity Manager worktree change. Use after implementing repository changes or before claiming they are validated; do not use for read-only analysis.

설치로 이동

소스 정보

저장소
Draculabo/AntigravityManager
최근 소스 활동
2026년 8월 25일 06:02
감지된 SKILL.md 언어
영어
스타
2,263
포크
276

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

SKILL.md 표시 중

SKILL.md
소스 지침 · 읽기 전용 미리보기
name
agm-validate-change
description
Select and run the smallest reliable validation set for an Antigravity Manager worktree change. Use after implementing repository changes or before claiming they are validated; do not use for read-only analysis.
# Validate an Antigravity Manager Change Validate the behavior a diff can affect without reflexively running the full repository suite. [Testing strategy](../../../docs/testing.md) owns the change-to-evidence mapping; the nearest `AGENTS.md` owns additional requirements. ## Inspect the change 1. Confirm the repository root, branch and worktree status. 2. Inspect staged, unstaged and relevant untracked files without modifying unrelated user work. 3. Classify each changed path as documentation/governance, renderer UI, routing, IPC/preload, Electron main lifecycle, persistence/security, proxy protocol/server, build/update or shared contract. 4. Identify behavior that crosses more than one category; those paths need evidence from each affected side. ## Select evidence - Start with the owning unit or integration test file. - Add `npm run type-check` for shared types, public exports, IPC contracts and module-boundary changes. - Add `npm run check:agent-contracts` for `AGENTS.md`, governance docs, Agent Notes or project Skills. - Add focused Playwright evidence for user flows that require the packaged Electron boundary, not for a purely local component change. - Add packaging, native keyring, updater or live-provider evidence only when the diff can affect that environment-dependent path. - Use the full local rehearsal only when the change is repository-wide, CI is being diagnosed, or the user explicitly requests it. Do not use a passing mock-only test as proof of native Electron, keyring, installer or live-provider behavior. Do not repeat an already passing command unless later edits invalidated its evidence. ## Handle results If a relevant check fails, diagnose that failure before widening scope. Do not skip it, weaken assertions or attribute it to the environment without concrete environment evidence. Stop when fixing it would require authority or scope beyond the requested change. Report: - changed behavior and affected surfaces; - commands actually run and their results; - environment-dependent or broader checks not run; - residual risk that the executed evidence does not cover.
GitHub에서 보기