verify

Run privacy, git cleanliness, and push status verification gates.

53|27|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/andresharpe/dotbot-v3 --skill verify-andresharpe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/andresharpe/dotbot-v3/tree/main/profiles/default/prompts/skills/verify
Command: npx skills add https://github.com/andresharpe/dotbot-v3 --skill verify-andresharpe

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of checking your codebase for potential issues, ensuring it meets quality and security standards before committing or deploying.

Core Features & Use Cases

  • Privacy Scan: Detects sensitive information like API keys or passwords in your code.
  • Git Cleanliness Check: Verifies that there are no uncommitted changes outside of the designated .bot/ directory.
  • Git Push Check: Ensures all your local commits have been pushed to the remote repository.
  • Use Case: Before pushing a new feature, run this skill to automatically scan for secrets, confirm your working directory is clean, and verify that all your work is backed up remotely.

Quick Start

Run all verification gates to check for privacy issues, git cleanliness, and pushed commits.

Frequently Asked Questions about verify

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

FAQPage Schema
How do I automate pre-commit code quality and security checks?

Automate pre-commit code quality checks by running verification gates that scan for sensitive secrets, verify git cleanliness, and ensure local commits are pushed to the remote repository before deployment.

What is the best way to scan my codebase for API keys before a git push?

Scanning for API keys before a git push is handled by the privacy scan verification gate, which detects sensitive information like passwords and secrets in your codebase prior to commit.

Do I need PowerShell 7 to run git cleanliness verification scripts?

Yes, you need PowerShell 7 to run git cleanliness verification scripts, as the execution protocols require this specific environment to properly report uncommitted changes outside the `.bot/` directory.

Can I verify that all local commits are pushed to the remote repository automatically?

You can verify local commits are pushed to the remote repository automatically using the git push check gate, which confirms your working state is fully backed up remotely during pre-merge workflows.

What happens if I have uncommitted changes outside the .bot directory during a pre-merge check?

During a pre-merge check, uncommitted changes outside the `.bot/` directory will fail the git cleanliness verification gate, alerting you to resolve the working directory state before proceeding.