Agm Validate Change logo

Agm Validate Change

CommunityPopular
Draculabo
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.

Overview

PublisherDraculabo
RepositoryAntigravityManager
Skill nameagm-validate-change
Stars
2.4K
Forks
285
Bundled files
Instructions only
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by Draculabo on GitHub. Read the source before you install it.

Installation

Install the Agm Validate Change AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/Draculabo/AntigravityManager/tree/main/.agents/skills/agm-validate-change
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Draculabo/AntigravityManager.git /tmp/AntigravityManager
mkdir -p .claude/skills
cp -r /tmp/AntigravityManager/.agents/skills/agm-validate-change .claude/skills/agm-validate-change
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Agm Validate Change in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Agm Validate Change on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Agm Validate Change is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Validate an Antigravity Manager Change

Validate the behavior a diff can affect without reflexively running the full repository suite. Testing strategy 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.

Frequently asked questions

What does the Agm Validate Change AI skill do?

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.

Why use Agm Validate Change on TypingMind?

Because you install it once and use it with any model. Agm Validate Change is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Agm Validate Change in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Draculabo/AntigravityManager/tree/main/.agents/skills/agm-validate-change. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Agm Validate Change?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Agm Validate Change?

As many as you like. As long as a model supports skills, you can use Agm Validate Change with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Agm Validate Change AI skill free?

It is published on GitHub by Draculabo. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇