Loading...
Loading...
Found 3 Skills
Use when setting up or running hooks with prek in any repository. prek is a Rust drop-in alternative to pre-commit for running Git hooks that check, format, lint, and validate code and repository files. Prefer it when speed, workspace mode, built-in hooks, shared toolchains, or native TOML configuration matter.
Onboard prek (Rust-powered pre-commit) into any project and suggest hooks tailored to the language/framework. Use when the user says "add prek", "set up pre-commit hooks", "configure prek", "what hooks should I use", or when you notice a project without a prek.toml that would benefit from pre-commit checks. Also trigger when the user wants to add new hooks to an existing prek.toml, audit their hook config, or migrate from pre-commit to prek. Covers Rust, Python, TypeScript/JavaScript, Go, Ruby, and Shell projects. Do NOT use for husky, lint-staged, or CI pipeline hook configuration — this skill is specifically for prek.
Configure .gitattributes, .editorconfig, .gitignore, and Git LFS filters for a repository: normalize line endings, mark generated, vendored, and documentation paths for GitHub linguist, set per-language editor defaults, and merge .gitignore content from GitHub templates. Use when the user says "add .gitattributes", "fix line endings", "CRLF", "linguist", "mark generated files", "set up .editorconfig", "gitignore template", "git lfs", or invokes /repo-attributes. Do NOT use for prek or pre-commit hook configuration — use /prek. GitHub custom properties (organization-level metadata) are out of scope; this skill only touches per-repository attribute, editor, and ignore files. Community health files (README, LICENSE, CODE_OF_CONDUCT, CONTRIBUTING, SECURITY) belong to /oss-hygiene, not this skill.