skills.rest
clawperator
clawperatorOFFICIAL
Explore all skills by this author →
GitHub

repo-setup

Configure local git hooks path and executable permissions for repository clones.

2|Updated Feb 17, 2026
Search Tags:#automation#git#hooks#commit-message#repo-setup#local-config#one-time-setup
One-click install
npx skills add https://github.com/clawperator/clawperator --skill repo-setup-clawperator
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: repo-setup
Source: https://github.com/clawperator/clawperator/tree/main/.agents/skills/repo-setup
Command: npx skills add https://github.com/clawperator/clawperator --skill repo-setup-clawperator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Configure local git settings for a repository clone so commit messages are sanitized via hooks.

Core Features & Use Cases

  • One-time repository setup for a clone.
  • Enable local git hooks to sanitize commit messages before they are saved.
  • Quick verification and rollback safety for local configurations.

Quick Start

From the repository root, run the commands to set the hooks path to .githooks and to make the commit-msg hook executable.

Frequently Asked Questions about repo-setup

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

FAQPage Schema
How do I set up local git hooks to sanitize commit messages in a cloned repository?▼

To set up local git hooks for sanitizing commit messages, run git config core.hooksPath .githooks from the repository root and make the commit-msg hook executable. Verify the configuration using git config --get core.hooksPath.

What is the best way to apply one-time git hook configurations across multiple clones?▼

The best way to apply one-time git hook configurations is by running git config core.hooksPath .githooks in each freshly cloned repository. This ensures commit messages are consistently sanitized locally without modifying global settings.

Do I need to make git hooks executable after setting the core.hooksPath?▼

Yes, you need to make the git hooks executable after setting core.hooksPath to .githooks. This ensures the commit-msg hook has the necessary permissions to run and sanitize commit messages before they are saved.

Can I verify that my local repository hooks are configured correctly?▼

You can verify your local repository hooks configuration by running git config --get core.hooksPath. This command checks if the hooks path is correctly set to .githooks for sanitizing commit messages.

When should I apply one-time local git configurations for commit messages?▼

You should apply one-time local git configurations for commit messages whenever you clone a fresh repository or encounter a subsequent clone where sanitized commit messages are required. This ensures consistent hook enforcement locally.

Why are my local git hooks not working after cloning the repository?▼

Local git hooks may not work after cloning if you have not applied the one-time setup. Ensure you run git config core.hooksPath .githooks and make the hooks executable, then verify with git config --get core.hooksPath.

Related Skills

Explore More Software Engineering Skills→
rahulrajaramrahulrajaram

install-commithooks

Install shared commithooks dispatchers and library modules into a git repository.

Community
Advanced
HyperxqHyperxq
1

lefthook

Enforce Conventional Commits and run Git hooks via Lefthook.

Community
Intermediate
Marshall-HallenbeckMarshall-Hallenbeck
5

safe-commit-all

Group working-tree changes into conventional git commits with issue references.

Community
Intermediate
ctrsploitctrsploit
153

commit-message

Generate semantic Git commit messages from staged changes using Conventional Commits.

Official
Intermediate