Showing 43501–43530 of 43639 skills
Operate a machine set up by urmzd/dotfiles through its `dotfiles` CLI: install or remove optional tools from the package catalog, diagnose a broken setup with `dotfiles doctor`, update the CLI, dotfiles, or packages, and add company tools to a pack's catalog.toml, and stack packs (company, team, role overlays). Use when the user says "install linear", "remove discord", "what can I install", "why is python broken", "update everything", "add our VPN for everyone at work", "add the backend-engineer pack", or "is this machine healthy". Do NOT use for editing the chezmoi source repo itself (templates, run_ scripts, naming; use dotfiles), for a project's own toolchain or .envrc (use setup-devenv), for colors and themes (use manage-theme), or for a known shell/nvim/gpg error signature (use triage-dotfiles-env).
urmzd/dotfiles
1Password-based secret storage workflow: vault layout, 1p:// references in .envrc, op run for local execution. Use when storing or rotating credentials with 1Password. (Other backends not covered.)
urmzd/dotfiles
Switch, create, or debug the color theme of a machine set up by urmzd/dotfiles: one theme colors Ghostty, Neovim (colorscheme and lualine), tmux (catppuccin flavour and colors), and the dotfiles' own output. Covers `dotfiles theme` / `dotfiles theme set`, writing a themes/<name>.toml or a pack's theme.toml, and per-shell output overrides (DOTFILES_UI_*). Use when the user says "switch to tokyonight", "change my terminal colors", "make a theme for our team", "my nvim colors did not change", or "use ASCII output in CI". Do NOT use for a project's brand identity, fonts, or demo capture (use style-brand), for installing apps or other machine upkeep (use manage-machine), or for editing unrelated chezmoi templates (use dotfiles).
urmzd/dotfiles
Drive an existing pull request to a mergeable state: get CI green, resolve merge conflicts with the base branch, address and resolve review comments, trigger required bot reviews/approvals (e.g. commenting '@claude review'), link associated issues, and clean up the PR title and description. Ends with a readiness report listing any remaining human-only blockers (required reviewer approvals, CODEOWNERS). Uses the CLI matching the repo's forge: gh for GitHub, glab for GitLab merge requests, tea for Gitea/Forgejo. Use when the user says "get this PR ready to merge", "make this PR mergeable", "get the PR green", "address the review comments", "babysit this PR", "get this MR merged", or "why is this PR blocked". Do NOT merge the PR or enable auto-merge; do NOT open a new PR (use pr); do NOT use for a failing pipeline with no PR context (use fix-and-retry / diagnose-ci).
urmzd/dotfiles
Orchestrate multiple agent CLIs (Claude, Codex, Antigravity) via tmux with a shared fleet store, dispatching one guardian subagent per pane. Survey-first: inspects and adopts existing tmux sessions, windows, and agent panes before creating anything new. Use when running a multi-agent session, dispatching parallel work, or coordinating subagents across panes.
urmzd/dotfiles
Open a pull request via gh pr create with a reviewer-ready body: What, Why, How, Verification with real evidence, and a Demo (screenshot, GIF, terminal capture, or plan output). Follows the repo's pull_request_template.md when one exists. Use when the user says "create a pull request", "open a PR", "gh pr create", "raise a PR", or "make a PR for this branch", and whenever an agent opens a PR as part of a larger task. Also use to rewrite the body of a thin existing PR (gh pr edit). Assumes commits already exist and only opens the PR. Do NOT commit changes or watch CI (use ship); do NOT diagnose or fix a failing pipeline (use fix-and-retry / diagnose-ci).
urmzd/dotfiles
Publish notes from an Obsidian vault folder into another folder (usually a repo's content directory) by one-way mirroring top-level Markdown files (add, update, remove). Discovers vaults and likely targets, asks the user where to publish from and to, previews, then mirrors with a bundled script. Use when the user says "publish the blog", "sync the vault to the repo", "push my Obsidian posts", or "publish-vault". Do NOT commit or push (use ship); do NOT edit note content.
urmzd/dotfiles
Audit GitHub releases, git tags, and release assets for one repo or every repo in a directory. Flags orphaned tags, missing binaries/checksums, draft releases, floating tag drift, pre-release remnants, and (when sr.yaml is present) sr config issues. Read-only: never deletes or modifies tags/releases. Use when checking "release health", "orphaned tags", "missing assets", "draft releases stuck", or "is sr.yaml configured right". Do NOT use to cut or publish a release, and do NOT use to set up the release pipeline -- this only audits and reports.
urmzd/dotfiles
End-to-end repo bootstrap: creates the GitHub repo (gh repo create), adds an Apache-2.0 LICENSE, dispatches to scaffold-project for CI/release/config, invokes community-health, writes a README, sets topics/description, and makes the initial commit and push. Use when starting a brand-new project from zero and you need the GitHub repo, metadata, and first push handled, not just local files. Do NOT use to scaffold files inside an existing repo; invoke scaffold-project directly for that.
urmzd/dotfiles
Scan a folder of git repos and report each repo's local dirty/clean state, ahead/behind divergence from upstream, recent activity, and latest CI run status. Read-only: never commits, pushes, or edits. Defaults to the folder argument or your repo root. Use when checking "what's live", "which repos are dirty", or "repo status across my projects". Sibling skills overlap on folder scanning: do NOT use for "what should I work on next" prioritization (use get-work); do NOT use for a recent-activity-only overview without dirty/CI detail (use status). repo-status is the local dirty/ahead/behind + CI-state report.
urmzd/dotfiles
Pragmatic Programmer principles: DRY, orthogonality, ETC, reversibility, tracer bullets, design by contract, decoupling/Law of Demeter, pragmatic paranoia. The 'why' layer between assess-quality (framework) and write-code (operational). Use when reasoning about design tradeoffs, coupling, or whether a decision is reversible. Do NOT use for the underlying quality framework (use assess-quality) or for concrete tool/idiom/library picks (use write-code).
urmzd/dotfiles
Standardized review of the CURRENT working-tree changes -- staged, unstaged, and untracked -- against an explicit five-dimension rubric (correctness, security, tests, scope-creep, conventions). Emits a prioritized findings list, each with file:line, severity, and a suggested fix. Read-only: it reviews and reports, it does not commit, push, or edit. Use when the user says "review my changes", "review the diff", "look over my staged changes before I commit", or "what's wrong with this PR locally". Do NOT use for red CI/pipeline failures (use diagnose-ci) or whole-repo quality-framework questions (use assess-quality); this reviews the working-tree diff only. assess-quality and review-design both EXCLUDE day-to-day review and name this skill as its home.
urmzd/dotfiles
Run a project's own eval suite end to end without babysitting: locate the harness, launch it in the background, monitor to completion, parse the report into a normalized summary (pass rate, latency percentiles, tokens, cost), and diff against the previous run with per-case regressions explained. Use when asked to "run the evals", re-run after a change, or score a new dataset in any repo with an eval harness. Do NOT use for the GAP benchmark suite (use run-evals), SAIGE provider-boundary checks (use verify), or designing new eval sets (that is authoring work, not a run).
urmzd/dotfiles
Owns where documentation lives: the root-file allowlist (README, CONTRIBUTING, USAGE, CODEOWNERS and the other GitHub and tooling files) and the docs/ taxonomy (architecture, adrs, rfcs, guides, reference, runbooks, plans) with templates for each kind. Scaffolds docs/ for a new repo, moves misplaced docs into it, and retires stale ones (finished plans, superseded decisions, duplicated upgrade notes). Use when creating docs/, adding an ADR, RFC, guide or runbook, asked to "clean up stale docs", "organize docs", or when a doc sits at the repo root or in the wrong docs/ folder. Do NOT use for prose cleanup (use clean-docs), drift between docs and code (use sync-docs), README structure (use write-readme) or AGENTS.md (use configure-ai).
urmzd/dotfiles
Scaffold a complete Go project with CI/CD, release pipeline, Makefile, sr.yaml, .envrc, and standard files. Uses go toolchain and make as the native build system. Loads on top of scaffold-project (run that first for cross-language standard files). Use when creating a new Go CLI, service, or module, or when the user mentions "new Go project", "go mod init", or "Go scaffold". Do NOT use for Rust, Python, Node, or Terraform projects; use the matching scaffold-<lang> skill.
urmzd/dotfiles
Scaffold a complete Node/TypeScript project with CI/CD, release pipeline, sr.yaml, .envrc, and standard files. Uses pnpm and biome. Loads on top of scaffold-project (run that first for cross-language standard files). Use when creating a new Node.js app, TypeScript library, or website, or when the user mentions "new Node project", "pnpm init", "TypeScript scaffold", or "Astro site". Do NOT use for Go, Rust, Python, or Terraform projects; use the matching scaffold-<lang> skill.
urmzd/dotfiles
Generates cross-language standard files (README, AGENTS.md, LICENSE, CONTRIBUTING.md, SECURITY.md, sr.yaml, .envrc, llms.txt), documentation conventions, and project structure, then dispatches to language-specific scaffolds. Use first for cross-language standard files and structure, THEN load the matching scaffold-<lang> skill (scaffold-rust, scaffold-go, scaffold-python, scaffold-node, scaffold-terraform) for CI/CD, release pipelines, and tooling. Use when creating or standardizing projects. Do NOT use alone for a single-language project; co-load the matching scaffold-<lang> skill for its CI/CD and tooling.
urmzd/dotfiles
Scaffold a complete Python project with CI/CD, release pipeline, justfile, sr.yaml, pyproject.toml, .envrc, and standard files. Uses uv, ruff, and justfile (Python lacks a native task runner like pnpm scripts, so just fills that gap). Loads on top of scaffold-project (run that first for cross-language standard files). Use when creating a new Python CLI, library, or application, or when the user mentions "new Python project", "uv init", or "Python scaffold". Do NOT use for Go, Rust, Node, or Terraform projects; use the matching scaffold-<lang> skill.
urmzd/dotfiles
Scaffold a complete Rust project with CI/CD, release pipeline, and sr.yaml. Uses cargo as the native build system. Loads on top of scaffold-project (run that first for cross-language standard files). Use when creating a new Rust CLI, library, or workspace, or when the user mentions "new Rust project", "cargo init", or "Rust scaffold". Do NOT use for Go, Python, Node, or Terraform projects; use the matching scaffold-<lang> skill.
urmzd/dotfiles
Scaffold a Terraform infrastructure project with CI/CD (plan on PR, apply on push), AWS OIDC auth, .envrc, and standard files. Uses terraform CLI as the native tool. Loads on top of scaffold-project (run that first for cross-language standard files). Use when creating infrastructure repos, or when the user mentions "new Terraform project", "terraform init", "AWS infra", or "infrastructure scaffold". Do NOT use for Go, Rust, Python, or Node application projects; use the matching scaffold-<lang> skill.
urmzd/dotfiles
Defines GitHub Actions workflow structure: ci.yml + release.yml naming, concurrency groups, bot-commit skip, workflow_call reuse, App-token checkout, and optional fsrc/teasr steps. Language-specific pipelines live in scaffold-rust, scaffold-go, scaffold-python, scaffold-node, scaffold-terraform. Use when setting up GitHub Actions, wiring ci.yml/release.yml, configuring concurrency or workflow_call, or adding fsrc/teasr steps. Do NOT use for sr.yaml schema, typed publishers, or the sr CLI/action; use sync-release for those.
urmzd/dotfiles
Per-language runtime version managers (fnm, uv, rustup) plus the vanilla-direnv .envrc pattern (layout python, use fnm, PATH_add, dotenv, source_up) for project dev environments. Use when bootstrapping a project's local toolchain, choosing a version manager, or writing a project .envrc. For chezmoi-managed pinned installer scripts and the tracked dot_envrc.project.example template, use setup-devenv-with-chezmoi.
urmzd/dotfiles
Chezmoi-specific dev environment helpers: writing pinned-version installer scripts (run_onchange_after_install-<tool>.sh.tmpl), maintaining the dot_envrc.project.example template, and the chezmoi diff/apply loop. Use when wiring a new pinned vendor installer (gcloud, aws-cli, Cortex) for the portfolio or scaffolding a chezmoi-tracked project envrc. Do NOT use for portable per-language version-manager or vanilla-direnv patterns; those live in setup-devenv.
urmzd/dotfiles
Generate a conventional commit message from staged or unstaged changes and create an atomic commit, then optionally push and watch CI until it passes or fails. Use when the user says "write a commit", "generate a commit message", "commit this", "git add .", or "ship this". Push and CI-watch are optional and skipped if the user only wants a commit. Do NOT open a pull request (use pr); do NOT diagnose-then-fix a failing pipeline (use fix-and-retry); do NOT do a read-only CI investigation without committing (use diagnose-ci).
urmzd/dotfiles
Establish a project's visual identity and apply the shared website design approach: readable typography, mobile navigation, clear visitor journeys, accessible interactions and consistent content. Use when designing or refining a website, interface, agent workspace or brand. Also covers terminal themes and demo assets.
urmzd/dotfiles
Audit and synchronize project documentation. Enforce clean prose, no em dashes, evidence-backed accuracy, current embedded examples, command drift checks, and cross-reference consistency. Use after feature changes, refactors, stale docs, README/AGENTS/llms.txt edits, or when the user asks to clean up docs. Delegates file-specific structure to owning skills.
urmzd/dotfiles
Audit one repository against ecosystem conventions (naming, capabilities, terminology, doc coverage, version discipline, canonical skill coverage) and emit a read-only drift report. Use when onboarding a repo, auditing convention drift, or checking ecosystem consistency after a refactor. This skill only reports; it never edits the target repo or the skill store. Do NOT use for applying fixes back into the chezmoi-managed canonical store; use sync-ecosystem-to-chezmoi for that.
urmzd/dotfiles
Take a drift report from sync-ecosystem and apply its fixes to the chezmoi source directory (create/edit skill dirs, assets, scripts), then run chezmoi apply so the canonical skill store and deployed copies stay in sync. Use when you maintain agent skills in chezmoi and have a pending drift report to merge back, or to promote a skill from a project repo into the canonical store. Do NOT use to generate a drift report or audit a repo; run sync-ecosystem first for that.
urmzd/dotfiles
Owns release-pipeline conventions: sr.yaml schema, the sr CLI verbs (init/plan/prepare/ release) and urmzd/sr action, typed publishers (cargo/npm/pypi/docker/go/custom), monorepo workspace discovery, version_files/stage_files mapping, and post-release patterns. Language-specific build targets live in scaffold-rust, scaffold-go, scaffold-python, scaffold-node. Use when writing or editing sr.yaml, choosing a publisher, or wiring the sr action. Do NOT use for GitHub Actions workflow file structure, ci.yml/release.yml naming, concurrency, workflow_call, or the App-token checkout; use setup-ci for those.
urmzd/dotfiles
Testing philosophy, test types (unit, integration, golden, fuzz, property, benchmark, smoke, E2E), per-language conventions (Rust, Go, Python, TypeScript), file organization, fixtures/mocks, CI strategy, and what NOT to test. Use when writing tests, reviewing test coverage, setting up test infrastructure, or deciding what to test. Do NOT use for general implementation patterns or error handling (use write-code) or design-by-contract reasoning (use review-design).
urmzd/dotfiles