Git Hooks

What This Skill Does

The Git Hooks skill allows you to automate critical development tasks by managing Git hooks directly from the OpenClaw interface. It simplifies the setup and maintenance of local scripts that run before and after Git operations like commit and push. Whether you need to enforce coding standards, run test suites, or validate commit messages, this tool provides a robust framework to implement these checks consistently within your Git repository.

Installation

To integrate this skill, run the following command in your terminal: clawhub install openclaw/skills/skills/sa9saq/git-hooks. Once installed, ensure you are operating within the root directory of a initialized Git repository, as the skill validates the presence of a .git/ folder before applying any hooks.

Use Cases

This skill is perfect for teams and individual developers looking to improve code quality. Use cases include:

1. Automated Linting: Ensure that your staged code adheres to style guides (e.g., ESLint for JS, pylint for Python) before it enters the commit history.
2. Quality Assurance: Automatically trigger your testing suite before code is pushed to remote branches to prevent broken builds.
3. Commit Governance: Enforce 'Conventional Commits' standards, which improves history readability and helps generate automated changelogs.
4. Security Hardening: Detect accidentally included credentials, such as API keys or secret tokens, before they are uploaded to public or shared repositories.

Example Prompts

1. "Setup a pre-commit hook that runs ESLint on all staged JavaScript files to ensure code quality."
2. "Add a commit-msg hook that rejects any commit messages that do not follow the conventional commit format."
3. "Create a pre-push hook that runs my test suite and aborts the push if any tests fail."

Tips & Limitations

• Bypassing: If you need to make a quick commit without running hooks, use the --no-verify flag with your git command.
• Performance: Keep your hooks lightweight. Long-running tasks should be kept under 5 seconds to ensure a smooth developer experience. Always target only the staged files rather than the entire directory.
• Compatibility: Always use /bin/sh for scripts to maximize cross-platform compatibility.
• Sharing: Since .git/hooks/ are not tracked in the repo, consider using git config core.hooksPath to point to a version-controlled directory if you wish to share these hooks with your team.