plugins/dev-tools/skills/hk/SKILL.md
Use when hk.pkl exists in project, hook output shows hk running, or working with git hooks in hk-managed projects. Also use when setting up, configuring, or troubleshooting hk git hooks.
npx skillsauth add technicalpickles/pickled-claude-plugins hkInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
hk is a fast git hook manager by jdx (author of mise). Uses pkl configuration language. Provides 90+ built-in linters.
Docs: https://hk.jdx.dev/ GitHub: https://github.com/jdx/hk
Identify which hook manager a project uses:
| File | Hook Manager |
|------|--------------|
| hk.pkl | hk |
| lefthook.yml | lefthook |
| .husky/ directory | husky |
| .pre-commit-config.yaml | pre-commit (python) |
hk init # Create initial hk.pkl
hk install # Set up git hooks
hk check # Run checks manually (read-only)
hk fix # Auto-fix issues
hk builtins # List available builtins
hk validate # Validate config
hk config dump # Show effective configuration
Builtins.pkl--profile slow)When editing hk.pkl, read hk-pkl-reference.md in this skill directory for structure and examples.
When looking up builtins, read builtins-reference.md in this skill directory. Or run hk builtins for the live list.
Stable reference: Read the reference files in this skill directory when needed.
Latest docs:
npx @mdream/crawl https://hk.jdx.dev/ --output /tmp/hk-docs
GitHub issues:
gh issue list -R jdx/hk # List open issues
gh search issues --repo jdx/hk "error" # Search issues
gh issue view 123 -R jdx/hk # View specific issue
Hook not running:
hk install # Reinstall hooks
cat .git/hooks/pre-commit # Verify hook calls hk
Step skipped:
hk check -v # Verbose output shows skip reasons
hk config dump # Check effective configuration
Validate config:
hk validate # Check hk.pkl syntax
tools
--- name: writing-for-scannability description: Use when structuring prose so readers can skim it - drafting or restructuring READMEs, docs, PR or issue bodies, design docs, RFCs, or any long-form text where a wall of prose hides the structure. Also use when explicitly asked to make something scannable or skimmable, convert prose to a list, surface a buried list, fix a wall of text, or decide whether bullets or prose fit. Strong signal: text with parallel sentence shapes, contrast markers ("that
development
Ignore actually-lsp nudges for an ecosystem in this project. Use when the user wants to silence, dismiss, or ignore the LSP setup nudges for a specific ecosystem (Rust, TypeScript, Ruby), or invokes `/actually-lsp-ignore` directly. Writes `dismissed=true` to `.claude/actually-lsp.json`. Persistent across sessions for this project only.
tools
Diagnose and fix LSP setup for the current project's detected ecosystems (Rust, TypeScript, Ruby). Use when the SessionStart hook nudged about a missing LSP plugin, when the env isn't ready (no `bundle install`, no `cargo build`, missing server binary), when LSP calls are failing, or when the user invokes `/actually-lsp-doctor` directly. Walks the per-ecosystem state machine, reports what's missing, then runs the fix.
tools
--- name: investigating-runs description: Use whenever the user mentions a GitHub Actions / GHA run, even casually — invoke this skill before reaching for raw `gh` commands, because the bundled `gha-snapshot` helper distills `gh run view --log-failed` (a firehose) into a readable block with per-job status, failed-step log tails, and annotations. Specific triggers (any one is enough): a `github.com/.../actions/runs/...` URL; the phrase "GitHub Actions" or "GHA"; the `gh run` CLI; a failing workfl