Skip to content
Agentmart
Submit a tool

aim-gitops

Automates the strict GitOps worktree and TDD workflow (formerly `aim fix` and `aim promote`) natively using PowerShell and git.

Skill by BrianV1981

IndexedMIT★ 3
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/brianv1981-aim-gitops

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Automates the strict GitOps worktree and TDD workflow (formerly `aim fix` and `aim promote`) natively using PowerShell and git.

Use cases: testing, productivity

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md and code. Checked Oct 26, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/aim-gitops

What's inside

Skill name
aim-gitops
Description
Automates the strict GitOps worktree and TDD workflow (formerly `aim fix` and `aim promote`) natively using PowerShell and git.
License
MIT
Instructions
44 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# `aim-gitops`

> **MANDATE:** Use this skill to spawn isolated git worktrees for development (fixing bugs/issues) and for promoting those changes back to the main branch natively on Windows. You are strictly bound by the rules of Surgical Staging and Test-Driven Development (TDD).

## 1. Spawning the Sandbox (The `fix` operation)
When assigned a code/config task or issue (e.g., issue 42), do NOT perform development directly on `main` *(Note: Agent Memory in `memory-wiki/**` and `HANDOFF.md` is living OS state exempt from worktrees/issues and is committed/pushed directly to `main`)*.
1. Ensure you are at the repository root.
2. Execute the native git worktree command: 
   `git worktree add -b fix/issue-42 workspace/issue-42`
3. **CRITICAL:** Change your working directory (`Cwd`) for all subsequent coding and testing to `workspace/issue-42`. Do not pollute the root repository.

## 2. Test-Driven Development (TDD)
While operating in your sandbox:
1. Write tests before or alongside your implementation.
2. **Empirical Proof:** You must prove the code works by running the test suite in your worktree. Never rely on blind output.
3. Do not proceed to staging or promotion until tests pass.

## 3. Surgical Staging
When preparing to commit your work:
1. **Never use `git add .` blindly.** 
2. Use `git status` to identify modified files.
3. Explicitly stage only the specific files necessary for the fix using `git add <file_path>`. This prevents localized test artifacts or scratch files from polluting the commit.
4. Commit with a descriptive message.

## 4. The Teardown (The `promote` operation)
Once your code is empirically proven to work (TDD) and surgically committed:
1. Return your working directory to the root of the repository.
2. To cleanly merge the worktree into the main branch, archive the previous main state, and tear down the worktree, run this exact sequence in PowerShell:
   ```powershell
   git checkout main
   
   # Archive the current main state for safety
   $archiveBranch = "archive/main-$(Get-Date -Format 'yyyyMMddHHmmss')"
   git branch $archiveBranch
   
   # Safely merge your fix
   git merge fix/issue-42
   
   # Cleanly delete the isolated workspace
   git worktree remove workspace/issue-42
   git branch -d fix/issue-42
   ```
3. After teardown, notify the operator that the promotion is complete.

From BrianV1981/aim-skill-library, MIT.

More from BrianV1981/aim-skill-library

Signals

Stars
3
Forks
0
Open issues
6
Last commit (this folder)
Oct 21, 2026 (7 days ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from BrianV1981

Cite this page

aim-gitops skill. Agent Mart. https://agentmart.dev/skills/brianv1981-aim-gitops (last updated 2026-10-24)