skills.rest
alangeb
alangebCOMMUNITY
Explore all skills by this author →
GitHub

git-verify

Analyze git diff statistics and scan for debug artifacts.

Updated Jun 22, 2026
Search Tags:#git#debugging#review#diff#code-quality#verify
One-click install
npx skills add https://github.com/alangeb/tau --skill git-verify
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-verify
Source: https://github.com/alangeb/tau/tree/main/src/skills/git-verify
Command: npx skills add https://github.com/alangeb/tau --skill git-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the risk of committing unintended code changes or debug artifacts by providing an automated, structured verification layer before finalizing git commits.

Core Features & Use Cases

  • Diff Statistics: Quickly summarize modified files and change counts to ensure the scope of work is as expected.
  • Debug Code Detection: Automatically scan for common debug patterns like print statements, breakpoints, or TODO/FIXME tags that should not reach production.
  • Use Case: Before pushing a feature branch, use this skill to confirm that only the intended files were modified and that no accidental debug prints remain in the codebase.

Quick Start

Use the git-verify skill to check the current directory for modified files and leftover debug code.

Frequently Asked Questions about git-verify

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

FAQPage Schema
How do I check git diff statistics before committing to ensure only intended files were modified?▼

To detect leftover debug code like print statements and breakpoints in a git repository, use an automated verification skill to scan diff changes for common debug artifacts and TODO/FIXME tags before pushing code.

What is the best way to automate pre-commit code review preparation and quality assurance?▼

The best way to automate pre-commit quality assurance is to run a verification script that analyzes git diff statistics and scans for debug artifacts, providing a structured validation layer before finalizing commits.

Do I need Python 3 and standard git CLI tools to run automated diff analysis and pattern matching?▼

Yes, you need Python 3 and standard git CLI tools installed in your environment to execute the diff analysis and pattern matching required for scanning repository changes and debug artifacts.

How do I scan my feature branch for accidental debug prints before pushing to production?▼

To scan a feature branch for accidental debug prints before pushing, run an automated verification process that checks the current directory for modified files and leftover debug code using pattern matching.

Can I automatically find TODO and FIXME tags in my git diff before finalizing a commit?▼

Yes, you can automatically find TODO and FIXME tags in your git diff by running a verification skill that scans repository changes for common debug patterns and artifacts that should not reach production.

Related Skills

Explore More Software Engineering Skills→
agentclashagentclash
25

git-rules

Validate git commit hygiene and working tree status post-commit.

Official
Basic
mhattingpetemhattingpete
657

git-pushing

Stage, commit, and push code changes with conventional commit messages.

Community
Basic
Chang-Shih-YungChang-Shih-Yung

health

Aggregate type checker, linter, and test results into a 0-10 composite score.

Community
Advanced
dollspace-gaydollspace-gay
6

review-pre-commit

Scan working code diffs for stubs, debug leftovers, and crosslink documentation.

Community
Intermediate