pre-commit conventions — never use Docker-backed hooks, always run
leroyguillaume/claude
SkillsMP has collected 19 skills from leroyguillaume/claude. Open a skill to review its source and details.
- Latest recorded source activity
- SkillsMP catalog refreshed
- skills collected
- 19
- GitHub stars
- 4
- GitHub forks
- 2
Skills in this repository
Showing 19 of 19 collected skills.
YAML formatting conventions (block style only, no flow style, no `
GitHub Actions / CI conventions (canonical quality/build/chart/release
Dockerfile conventions (minimal CVE-free base images —
Rust project conventions (clap, tokio, axum, tracing, mockall,
Helm chart conventions (values structure, security context,
Kubernetes operator / controller conventions (error handling,
kopf-specific mechanics for Python Kubernetes operators — event
GitHub repository settings administered via the `gh` CLI — sync
Conventions for opening GitHub pull requests with the `gh` CLI —
Python project conventions (uv, ruff, typer, pydantic, Pylance).
HTTP/RPC API conventions (dedicated DTOs, no domain models on the
SQL linting/formatting conventions (always sqlfluff).
Docker Compose conventions (file naming).
Frontend project conventions (TypeScript, React, Biome, enforced
Logging and observability conventions (liberal debug logs,
Ollama model-selection conventions (never recommend a model from
Project metadata conventions (derive author/maintainer and
Signal handling and graceful shutdown conventions for long-running