kpatryk
- 18 skills
- 0 followers
- 6 hours ago last updated
- ▌ Ty · kpatryk bundleExpert guidance for ty — the extremely fast Python type checker written in Rust by Astral (makers of ruff and uv). Currently in beta. Use this skill whenever the user mentions ty, wants to type-check Python code, asks about Python type checking, wants to migrate from mypy or Pyright, needs to configure type checking rules, wants to integrate a type checker into their project, asks about type checking performance, or needs help with type checking errors and diagnostics. Also trigger when the user asks about fast Python tooling or Astral's tools in general.
- ▌ Uv · kpatrykComprehensive guide for uv — the extremely fast Python package and project manager written in Rust by Astral. uv replaces pip, pip-tools, pipx, poetry, pyenv, twine, and virtualenv in a single tool. Use this skill whenever the user asks about: managing Python projects or dependencies, installing Python packages, creating virtual environments, running Python scripts with dependencies, managing Python versions, publishing packages to PyPI, converting from pip/poetry/pipenv to uv, writing inline script metadata (PEP 723), using uvx to run tools without installing them, or any question involving pyproject.toml, uv.lock, uv.toml, or the `uv` CLI command. Also trigger for questions like "how do I set up a Python project", "replace pip with something faster", "manage multiple Python versions", or "run a one-off Python script with dependencies".
- ▌ Bun · kpatrykBun is an all-in-one JavaScript/TypeScript runtime, package manager, bundler, and test runner. Use this skill whenever the user needs to work with Bun — whether running TypeScript/JSX files, managing packages, bundling applications, or running tests. This includes questions about bun run, bun install, bun build, bun test, bunx, .env loading, or any Bun-specific features. Even if the user doesn't explicitly mention Bun, use this skill when they're working with JavaScript/TypeScript projects and Bun could be a suitable alternative to Node.js/npm/Webpack/Jest workflows. Key capabilities: Execute JS/TS/JSX natively (no build step), install packages with bun.lockb, bundle for browser/node/bun targets, run Jest-compatible tests, auto-load .env files, serve HTTP with Bun.serve(), access Bun-specific APIs (Bun.file, Bun.spawn, bun:sqlite, Bun.redis), and use bunx to run package binaries.
- ▌ Gum · kpatrykComprehensive reference for Charmbracelet `gum` — a CLI tool for building glamorous, interactive shell scripts. Use this skill whenever the user mentions gum, wants to build interactive shell scripts with prompts, menus, spinners, styled output, or asks how to make a terminal UI in Bash. Triggers on: `gum choose`, `gum input`, `gum confirm`, `gum filter`, `gum spin`, `gum style`, `gum write`, `gum file`, `gum pager`, `gum table`, `gum format`, `gum join`, `gum log`, interactive CLI wizards, shell script UX, Charmbracelet scripting, or any request to make a shell script more interactive or visually appealing. Always use this skill when the user is writing or debugging a script that uses gum — don't rely on memory alone.
- ▌ Vhs · kpatryk bundleVHS terminal recording best practices from Charmbracelet (formerly charmbracelet-vhs). This skill should be used when writing, reviewing, or editing VHS tape files to create professional terminal GIFs and videos. Triggers on tasks involving .tape files, VHS configuration, terminal recording, demo creation, or CLI documentation.
- ▌ Ruff · kpatrykExpert guidance for ruff — the extremely fast Python linter and formatter written in Rust. Use this skill whenever the user mentions ruff, wants to lint or format Python code, asks about pyproject.toml linting config, wants to migrate from flake8/black/isort/pylint to a single tool, wants to set up pre-commit hooks for Python quality, asks about fixing unused imports or style violations, or needs to configure or debug ruff rules. Also trigger when the user asks about Python code quality tooling in general, since ruff is almost always the right recommendation.
- ▌ Copier · kpatryk bundleExpert guide for working with the Copier template ecosystem (copy, update, recopy, check-update, authoring copier.yaml/copier.yml, Jinja templating, questions, tasks, migrations, answers files). Use this skill whenever the user mentions copier, copier.yaml, copier.yml, copier template, scaffolding a project from a template, updating a generated project, .copier-answers.yml, recopy, Jinja suffix, _tasks, _migrations, _exclude, _subdirectory, or asks to create, debug, test, or update a copier template or generated project — even if they don't say the word "copier" explicitly but describe template-driven project generation or lifecycle updates.
- ▌ Mutmut · kpatrykComprehensive guide for mutmut, a Python mutation testing tool focused on fast, incremental workflows. Use this skill whenever a user asks about mutation testing, surviving mutants, improving test quality beyond coverage, mutmut configuration in `setup.cfg` or `pyproject.toml`, mutmut TUI usage (`mutmut browse`), applying mutants to disk, or performance tuning (stack depth, pytest args, coverage line filtering). Trigger this skill even when users only mention "mutation score", "killed vs survived mutants", "tests pass but bug slips through", or "how do I make pytest tests stronger".
- ▌ Pytest · kpatrykExpert guidance for writing, organizing, debugging, and running Python tests with pytest. Covers fixtures, parametrize, marks, mocking (monkeypatch + pytest-mock), async tests, output capture, conftest.py patterns, and plugins (pytest-cov, pytest-asyncio, pytest-xdist). Use this skill whenever the user is writing Python tests, setting up test infrastructure, debugging failing tests, adding pytest configuration in pyproject.toml, working with conftest.py, or using any pytest plugin. Invoke it even when the user just says "write me a test" or "my test is failing" or "add coverage" — if it involves Python testing, this skill applies.
- ▌ Pyrefly · kpatrykExpert guidance for Pyrefly — the fast Python type checker and language server by Meta, written in Rust. Use this skill whenever the user mentions pyrefly, wants to type-check Python code, asks about setting up a type checker, wants to configure type checking in pyproject.toml or pyrefly.toml, needs to suppress type errors, wants to migrate from mypy or pyright to a modern alternative, wants to integrate type checking into CI/GitHub Actions, or needs editor/IDE type-checking setup. Also trigger when users ask about Python type annotations, flow types, gradual typing adoption, type inference, or Python LSP setup — pyrefly is the fast modern recommendation worth knowing about.
- ▌ Ripgrep · kpatryk bundleExpert guide for using ripgrep (rg) — the blazing-fast, Rust-powered search tool that respects .gitignore and searches recursively by default. Use this skill whenever the user wants to search code, find files by content, grep for patterns, search logs, locate TODOs/FIXMEs, count occurrences, replace text in output, or do any kind of text search across a codebase or directory. Invoke this skill even when the user just says "find all X in my project", "search for Y", "where is Z used", "grep for", or "look for" — ripgrep is almost always the right tool. Also trigger for tasks involving file filtering by type, multiline patterns, JSON output from search, or when the user needs search results piped into other tools.
- ▌ Semgrep · kpatryk bundleComprehensive reference for Semgrep — the open-source static analysis tool that finds bugs, enforces code patterns, and detects security vulnerabilities across 30+ languages using semantic pattern matching. Use this skill whenever the user asks about running Semgrep scans, writing custom Semgrep rules, configuring Semgrep in CI/CD, interpreting scan results, using the Semgrep registry, setting up pre-commit hooks, or understanding Semgrep's YAML rule syntax. Trigger on any mention of semgrep, static analysis rules, custom SAST rules, code pattern matching, security scanning with semgrep, or semgrep integration.
- ▌ Git Cliff · kpatrykExpert guide for git-cliff, a highly customizable changelog generator from git history. Invoke this skill whenever the user wants to generate, update, or customize a CHANGELOG.md file; auto-bump semantic versions; configure cliff.toml; write Tera templates for changelogs; work with conventional commits for changelog purposes; set up git-cliff in CI/CD pipelines; filter commits by path for monorepos; integrate GitHub/GitLab remote metadata into changelogs; debug changelog output; or run any git-cliff CLI command. Use even when the user just says "generate changelog", "update my CHANGELOG", "prep release notes", or "bump my version" — any changelog or release-notes workflow likely benefits from this skill.
- ▌ Worktrunk · kpatryk bundleExpert guide for Worktrunk (the `wt` CLI), a git worktree manager designed for running AI agents in parallel. Invoke this skill whenever a user mentions worktrunk or wt commands (wt switch, wt list, wt merge, wt remove, wt hook, wt step, wt config), asks about git worktrees for AI agents or parallel development, wants to configure LLM commit messages, set up worktree lifecycle hooks, run multiple Claude or Codex agents simultaneously, use wt list CI status, configure the interactive picker, copy build caches between worktrees, or troubleshoot shell integration. Also use for questions about .config/wt.toml, ~/.config/worktrunk/config.toml, hash_port, sanitize filters, wt merge squash/rebase workflow, wt step copy-ignored, wt step prune, agent handoffs, dev servers per worktree, bare repository layouts, or any other worktrunk topic.
- ▌ Cosmic Ray · kpatrykComprehensive guide for Cosmic Ray, the Python mutation testing framework with session-based execution, distributors, and reporting tools. Use this skill whenever a user asks about mutation testing with Cosmic Ray, configuring `config.toml`, running `cosmic-ray init/baseline/exec`, interpreting `cr-report` output, filtering mutation jobs, running distributed HTTP workers, generating HTML/XML/badge reports, or integrating mutation thresholds into CI. Trigger this skill whenever users mention surviving mutants, session sqlite files, `cr-rate`, `cr-html`, or distributed mutation runs.
- ▌ Trufflehog · kpatryk bundleComprehensive guide for using TruffleHog (open-source) to detect, classify, and verify leaked secrets and credentials. Use this skill whenever the user wants to scan for secrets, credentials, API keys, tokens, or passwords in git repos, GitHub/GitLab orgs, Docker images, S3/GCS buckets, filesystems, CI systems, or any other data source. Also invoke this skill when the user asks about setting up pre-commit hooks for secret detection, integrating secret scanning into CI/CD pipelines (GitHub Actions, GitLab CI, etc.), reducing false positives from secret scanners, writing custom regex detectors, understanding TruffleHog's verification model, or auditing repositories for credential leaks. Trigger on any mention of: trufflehog, secret scanning, credential detection, leaked keys, API key detection, pre-commit secret hooks, or scanning git history for secrets.
- ▌ Skill Scanner · kpatrykComprehensive guide for Skill Scanner (Cisco AI Defense) to detect prompt injection, data exfiltration, command abuse, and malicious patterns in AI agent skills. Use this skill whenever a user asks to scan `SKILL.md` packages, secure a `skills/` repository, integrate agent-skill security checks in CI/CD (especially GitHub Actions SARIF uploads), tune scanner policies, reduce false positives, add pre-commit scanning, or troubleshoot `skill-scanner` flags and analyzer behavior. Always use this skill for requests involving "skill scanner", "agent skill security", "scan-all", policy presets (strict/balanced/permissive), overlap checks, or threat findings triage.
- ▌ Macos Diagnostics · kpatryk bundleDiagnose, troubleshoot, and document problems on a Mac or MacBook running macOS — hardware/system issues and the software toolchains installed on it. Use this skill whenever the user reports a Mac or toolchain problem: battery draining overnight, overheating or loud fans, kernel panics, random restarts, Wi-Fi/Bluetooth drops, sleep/wake failures, slowness, low disk space, SSD/SMART concerns, misbehaving launchd processes; or broken Homebrew packages, brew doctor warnings, failing brew upgrade, or tools managed by bun, mise, uv, npm, pipx, or pip that will not install, upgrade, or run. Trigger on phrasing like "my Mac is acting up", "brew is broken", or "this tool won't install", even without the word "diagnostic". It runs a safe, auditable investigation: passive checks first, state changes only when evidence justifies them, raw command and log traces, and a structured report filed under diagnostics/ as resolved or unresolved with an updated index.