dotfiles

Generate a standalone HTML report from a markdown file with d2 diagrams, SVGs, and syntax-highlighted code blocks. Use when the user asks for a report, a visual writeup, or a document with diagrams.

Interact with GitLab REST API using GITLAB_TOKEN - use for TODOs, repositories, CI/pipelines, MRs, issues, and other API queries

GitLab Development Kit is a folder and set of utilities that contain most of the GitLab production systems. This skill is useful for testing with local GitLab deployment and when researching how feature works in the GitLab monolith, AIGW, workhorse and other services

CRUD GitLab issues,MRs,pipelines,jobs,epics,issue comments

my projects — gitlab namespace and ID, where they live on the local drive. Use whenever a question references a project by name, alias, or path, or when you need to locate a repo locally. Keywords - project, repo, where does X live, local path, gitlab-lsp, glab, cli, vscode extension, note, task, duo cli, dotfiles.

code changes review, use this skill any time I ask you to review a change

Run an interactive CLI/TUI app in tmux, send it input, and read its output. Use to test interactive apps.

use this skill when you need to search the web, think google search for agents

Block execution until a condition is met. Use when waiting for pipelines, merge trains, deployments, file creation, or any event that can be checked with a shell command.

Use whenever the user mentions git worktree, creating a branch, or switching branches. Keywords - worktree, git wta, git wtu, bare repo, new branch, create branch.

Knowledge about Tomas's local dev environment and config — keyboard mapping (kanata), fish shell, terminal (ghostty), zellij, neovim, pi/qmd tooling, and the stow-managed dotfiles repo. Use whenever the user talks about their keyboard mapping, shell, terminal, editor, pi, or other local tools. Keywords - dotfiles, kanata, keyboard mapping, home row mods, hrm, fish, ghostty, terminal, zellij, neovim, nvim, vim.pack, qmd, mise, stow, espanso, yabai, skhd.

GitLab Development Kit (GDK) — local GitLab development environment. Use when the user mentions GDK, starting/stopping GitLab locally, running rails console, GDK services, or local GitLab development, or looking up something in the gitlab project. Keywords - gdk, gdk start, gdk stop, gdk update, gdk status, gdk reconfigure, local gitlab.

Git worktree and branch management using bare-repo layout. Use whenever the user mentions git worktree, creating a branch, or switching branches. Keywords - worktree, git wta, git wtu, bare repo, new branch, create branch.

Generate standalone HTML reports with dark theme, Mermaid diagrams, and auto-open in browser. Use when asked to create a report, analysis document, or visual summary.

Must read guide on creating/editing mermaid charts with validation tools

Content standards for writing GitLab merge request and issue titles, descriptions, and comments — formatting, structure, and conventions. Use whenever you create or update an MR/issue description or body, or write any comment. This is about WHAT to write, not how to call the API (see gitlab-api / gitlab-mr-comments for the commands). Keywords - MR description, issue description, MR title, issue title, conventional commit, Problem Solution, AI-generated.

Trigger native web search. Use when you need quick internet research with concise summaries and full source URLs.

Tomas's projects — what they are and where they live on the local drive. Use whenever a question references a project by name, alias, or path, or when you need to locate a repo locally. Keywords - project, repo, where does X live, local path, gitlab-lsp, glab, cli, vscode extension, note, task, duo cli.

ALWAYS use this skill before writing shell scripts that will be persisted. You don't have to use this if you are writing inline throw-away scirpts.

Capture terminal screenshots and GIF recordings from tmux sessions using freeze and agg. Use when you need to screenshot a TUI app, generate terminal images, or convert asciinema casts to GIFs.

Test interactive CLI applications using tmux sessions. Simple shell script helper for testing terminal apps.

Block execution until a condition is met. Use when waiting for pipelines, merge trains, deployments, file creation, or any event that can be checked with a shell command.

Allows to interact with web pages by performing actions such as clicking buttons, filling out forms, and navigating links. It works by remote controlling Google Chrome or Chromium browsers using the Chrome DevTools Protocol (CDP). When Claude needs to browse the web, it can use this skill to do so. Unless explicitely asked, never use this for GitLab access, use gitlab-api skill instead

SSH into the Windows 11 ARM64 test VM for PowerShell-based checks (e.g. gitlab-lsp Windows regression tests). Manual-invoke only.

Context about MRs, issues, TODOs, and code reviews the user is working on. Use whenever the question could benefit from knowledge of their active work, projects, or collaborators. Use EVERY time I mention board. Use when asked to save/create a reference or look up a past reference. Keywords - issue, work context.

Interact with GitLab REST API using glab CLI and GITLAB_TOKEN — use for pipelines, jobs, merge requests, issues, TODOs, merge trains, and other GitLab API queries