Prek
Make AI Agents great again!
npx -y skills add MAHDTech/agent-skills --skill prekAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Run pre-commit hooks using the prek CLI tool. Differentiates between 'pre-commit' (the git hooks concept/lifecycle stage) and 'prek' (the actual binary command; pre-commit CLI is deprecated, use prek). Use when you need to run, configure, check, or troubleshoot git pre-commit hooks.
SKILL.md
1.7 KB, 387 tokens by cl100k_base, as published. Nobody here has run it
Prek (Pre-commit)
prek is a fast Git hook manager written in Rust, designed as a drop-in replacement for the deprecated pre-commit CLI tool.
[!IMPORTANT] Command Line & Package Discrepancy: The CLI binary is
prek, NOTpre-commit. Thepre-commitCLI tool is deprecated and MUST NOT be used.
Key Differences
- Git concept / stage: "pre-commit" refers strictly to the Git lifecycle hook stage (e.g.
.pre-commit-config.yaml). - Legacy CLI Tool (DEPRECATED): The Python-based
pre-commitCLI tool is deprecated. NEVER addpkgs.pre-commitorpre-commitpackage/input todevenv.nixor package managers. - Active Hook Runner:
prekis the CLI binary used to run and configure pre-commit hooks.
Running Hooks
When working inside a devenv shell, run:
SECRETSPEC_REASON="running pre-commit hooks" devenv --no-tui shell -- prek run -a
If not using devenv, run:
prek run -a
Use -a or --all-files to run hooks against all files in the repository.
Commands
prek run: Run hooks against modified files.prek run -a: Run hooks against all files.prek install: Install prek Git shims into Git's hooks directory.prek uninstall: Uninstall prek Git shims.prek validate-config: Validate configuration files (prek.tomlor.pre-commit-config.yaml).prek cache: Manage the prek cache (e.g.,prek cache clean).
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most quality gates skills give in 387 tokens
Counted across 1,195 of the 2,094 authors here whose files we hold, read 2026-08-07
- Read the output and check the exit codein 54 of 1195, across 14 files
- Verify requirements using a line-by-line checklistin 53 of 1195, across 12 files
- Identify the verification command proving the claimin 51 of 1195, across 12 files
- Run the full verification commandin 50 of 1195, across 11 files
- Verify output confirms the claimin 49 of 1195, across 12 files
- Check version control diff after agent delegationin 46 of 1195, across 6 files
- State claim with evidencein 44 of 1195, across 4 files
- Run the test suitein 33 of 1195, across 26 files
- Keep state in memory by defaultin 27 of 1195, across 6 files
- Make prototype runnable with one commandin 26 of 1195, across 5 files
- Produce a verification reportin 25 of 1195, across 14 files
- Detect the package manager from lockfilesin 24 of 1195, across 5 files
Said here and by no other author read
- Use the `prek` CLI tool
- Run `prek run -a` to run hooks against all files
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.