More screenshots
Works with the AI tools you already use
Claude Code
Cursor
Codex CLI
Muse
Dots+22 moreClaude CodeCursorCodex CLIMuseDots
OpenClaw
Manus
Grok
Grok Bot+18 agentsGitGuard
Protect Git workflows from messy changes, risky operations, and release mistakes.
$9
GitGuard
Example session with this skill installed
Run GitGuard on my current repository before I open a pull request.
Inspect the current branch, working-tree state, staged and unstaged changes, untracked files, recent commits, diff scope, sensitive files, and branch relationship to the base branch.
Do not modify, delete, commit, reset, stash, clean, or rewrite anything.
Give me a complete GitGuard report showing what is clean, what needs attention, the risk level of each finding, and exactly what I should verify before opening the PR.
- Read your context and instructions
- Compiled the gitguard
- Generated the document
GitGuard Repository Report
Overall Status: NEEDS ATTENTION
GitGuard inspected the repository without modifying, deleting, staging, committing, stashing, resetting, or cleaning any files.
1. Repository State
| Check | Result |
|---|---|
| Repository | Detected |
| Current branch | feature/payment-retry |
| Working tree | Changes detected |
| Staged changes | Detected |
| Unstaged changes | Detected |
| Untracked files | 3 detected |
| Merge/rebase state | No active conflict state detected |
The repository is not currently clean, so the final PR scope should be reviewed before any commit or merge operation.
2. Branch Guard
Branch: feature/payment-retry
The branch has diverged from its upstream/base relationship.
Risk: MEDIUM
This does not automatically indicate a problem, but the branch relationship should be understood before opening or merging the PR.
Recommendation:
Review the commits that exist on the feature branch and compare them with the current base branch before deciding whether a merge or rebase is appropriate.
GitGuard does not automatically choose merge or rebase based on personal preference.
3. Working-Tree Guard
GitGuard detected
- Modified tracked files
- Staged changes
- Unstaged changes
- 3 untracked files
The untracked files should not be assumed to be disposable.
Risk: MEDIUM
Before committing, determine whether each untracked file is:
- Part of the feature
- A generated artifact
- A local-only file
- A temporary/debug file
- Potentially sensitive
- Unknown
No untracked files were deleted.
4. Diff Guard
The primary application changes appear related to the payment-retry feature.
However, one configuration file is outside the obvious feature scope.
Risk: HIGH
Configuration changes can affect environments beyond the immediate feature and may require separate review.
Recommendation:
Confirm whether the configuration change intentionally belongs in this PR.
Do not remove it automatically.
5. Sensitive File Guard
An environment-style file was detected.
Risk: HIGH
Environment files can contain API keys, database credentials, service tokens, or other sensitive configuration.
GitGuard did not display or reproduce any credential values.
Verify:
- The file is intentionally ignored.
- It is not staged.
- It is not part of the commit.
- No credentials have previously been committed to repository history.
If an actual credential has been exposed, removing the file alone may not be sufficient. The affected credential should also be rotated through the appropriate provider.
6. Commit Guard
Recent commits are generally understandable.
One commit contains a relatively broad group of changes.
Risk: MEDIUM
A broad commit can make code review and future troubleshooting more difficult.
Recommendation:
Determine whether the commit represents one coherent change. If the repository's workflow permits history editing and the commits are not shared, splitting them may be considered.
Do not rewrite history solely for stylistic reasons.
7. Verification
| Verification | Status |
|---|---|
| Repository inspection | ✓ Completed |
| Working-tree inspection | ✓ Completed |
| Diff inspection | ✓ Completed |
| Branch inspection | ✓ Completed |
| Sensitive-file review | ✓ Completed |
| Automated tests | ⚠ Not run |
| Lint | ⚠ Not run |
| Type checking | ⚠ Not run |
Tests, linting, and type checking are therefore not verified.
GitGuard Priority Findings
🔴 HIGH — Configuration change requires confirmation
A configuration file appears outside the primary feature scope.
🔴 HIGH — Environment-style file requires review
Confirm that it is ignored, unstaged, and not present in repository history with credentials.
🟠 MEDIUM — Branch divergence
Review the feature branch against its base before proceeding.
🟠 MEDIUM — Broad commit
Consider whether the commit accurately represents one coherent change.
🟡 MEDIUM — Verification incomplete
Relevant automated checks have not been run.
Recommended Next Actions
- Confirm whether the configuration-file change belongs to the PR.
- Confirm that the environment file is ignored and not staged.
- Review the three untracked files individually.
- Compare the feature branch with the current base branch.
- Inspect the final staged diff.
- Run the project's relevant tests, lint, and type checks.
- Only then prepare the final PR.
GitGuard Final Gate
PR Readiness: NEEDS ATTENTION
The repository has not been modified by GitGuard.
No files were deleted, reset, staged, committed, stashed, cleaned, or rewritten.
Next decision: resolve the identified findings and run the required verification before opening the PR.
gitguard.pdf
PDF · document
Example file from a real run - the skill writes it into your workspace.
Connects securely to your tools. The creator never sees your data.
What you get
About this skill
GitGuard is a safety-first Git workflow skill for AI coding agents.
It helps developers keep repositories clean, reviewable, and safer to modify by systematically inspecting Git state before important operations.
GitGuard checks:
- Repository and working-tree health
- Staged, unstaged, and untracked changes
- Branch state and divergence
- Diff scope and unrelated changes
- Sensitive files and credential exposure
- Commit and staging hygiene
- Pull-request readiness
- Merge and rebase safety
- Conflict handling
- Release readiness
Its core workflow is:
Inspect → Classify → Warn → Recommend → Authorize → Act → Verify
GitGuard is designed specifically for AI-assisted development, where an agent may otherwise make assumptions about repository state or perform unnecessary Git mutations.
It protects unexplained user work, avoids unnecessary destructive operations, and clearly separates what was observed, recommended, and actually executed.
Use it before committing, opening a PR, merging, rebasing, cleaning a repository, or preparing a release.
Built for developers and AI coding agents working with real Git repositories—not generic Git theory.
How to install
Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.
- 1
Download the ZIP
Free skills download straight away. Paid skills unlock right after purchase.
- 2
Unzip into your skills folder
Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.
- 3
Ask your agent to use it
Restart the agent if it was already running. It picks the skill up automatically - no config needed.
Skills folder by agent
Click the path to copy it. Create the folder if it does not exist yet.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill passes our trust checks below.
Security scanned
Passed our 8-point scan before listing
Fresh listing
Recently published to Agensi
30-day refund
Not a fit? Get your money back
Trust & safety
Security scanned
Verified clean 15 days ago
- Passed all security checks, Safe to install