dotfiles

Keep a GitLab issue's native Status in sync with its merge requests, and start implementing an issue by assigning it to the current user and setting the active milestone. Use when asked to start work on an issue, update an issue's status as MRs progress, or track issue state through the dev/review/complete lifecycle.

Run commands in a temporary tmux pane with full interactive zsh environment (login shell, shims, PATH, aliases, TTY).

Hammerspoon macOS automation. Config in ~/.hammerspoon/. Modules: init.lua, spaces, sleepwake, urlrouter, httpserver, meetings, webcam. Keywords: hammerspoon, hs, lua, audiodevice, hotkey, caffeinate, httpserver, Stream Deck, Rectangle Pro, blueutil, AirPods, URL routing, webcam, uhubctl. Use when: editing ~/.hammerspoon/ files, debugging Hammerspoon modules, adding Hammerspoon features, checking Hammerspoon logs.

Use before any Git branch operation in this repo. SSOT for the branch naming convention (<username>/<issue-id>/<branch-name>) — load before creating a branch instead of guessing the name. Also provides helpers for finding a branch's parent, rebasing related branches, force-pushing feature branches, and understanding commit or diff structure across stacked Git branches.

Iteratively test and refine prompts, skills, and agent configurations using opencode run

Inspect GitLab local ClickHouse tables, schemas, ingestion paths, and data patterns. Use for CH table questions, DESCRIBE TABLE, schema/source-of-truth checks under db/click_house, ClickHouse ingestion debugging, and investigating aggregates, distributions, or anomalous data in the GitLab repo.

Use when list, inspect, and undo branch-specific GitLab database migrations. Use for checking which migrations were introduced by the current branch, rolling them back safely, and understanding migration state during local GitLab database work.

Use when waiting for MR merge and trigger MR pipelines using glab CLI helpers

Inspect local GDK PostgreSQL test and development databases with gdk psql. Use for Postgres schema checks, table and index inspection, read-only SQL queries, migration verification, and investigating GitLab data in local test or dev databases.

Load and reconcile repo-local GitLab instructions before substantive work

Use when choosing the right lookup and execution tools for GitLab repo work

Recommend (or, on explicit request, assign) the best GitLab reviewers for a merge request, optimizing for outstanding review load, availability, OOO/PTO (current and upcoming), timezone fit, and the SME-then-maintainer review convention. Use when the user asks who should review an MR, to find/suggest reviewers, or to assign reviewers while creating MRs.

Handle GitLab Development Kit updates, local secrets, and GDK branch workflows. Use for fgdku-based updates, setting up GitLab secrets, managing branch-specific GDK state, and other local GitLab development environment operations.

Write a weekly status report on a GitLab issue or epic using a fixed template. Use when the user asks for a "weekly status", "weekly update", "status review", or "status update" on a specific work item.

Query the GitLab Knowledge Graph (Orbit) via the typed `glab orbit remote` CLI subcommands. Use for code-structure questions (who calls this function, where is this symbol defined), cross-project dependency and blast-radius analysis, merge-request and contributor queries, and any question answerable by traversing GitLab's unified entity graph (projects, users, MRs, issues, pipelines, files, definitions, vulnerabilities).

Automate GitLab issue, merge request, epic, and work-item workflows with glab. Use for viewing or updating GitLab metadata, creating or editing issues and MRs, handling epic comments through GraphQL, and other CLI or API-driven GitLab operations in the GitLab repo workflow.

GitLab merge request lifecycle helpers (push, test, tidy, apply patches)

GitHub workflow automation using gh CLI

Mise development environment manager (asdf + direnv + make replacement). Capabilities: tool version management (node, python, go, ruby, rust), environment variables, task runners, project-local configs. Actions: install, manage, configure, run tools/tasks with mise. Keywords: mise, mise.toml, tool version, runtime version, node, python, go, ruby, rust, asdf, direnv, task runner, environment variables, version manager, .tool-versions, mise install, mise use, mise run, mise tasks, project config, global config. Use when: installing runtime versions, managing tool versions, setting up dev environments, creating task runners, replacing asdf/direnv/make, configuring project-local tools.