Sponsored by

Find leads on Reddit on auto pilot

Topic: dotfiles

206 skills in this topic.

planning-write-a-prd Create a PRD by interviewing the user, exploring the codebase, and writing a structured YAML plan to ./plans/{slug}/prd.yaml. Use when user says "write a PRD", "plan this feature", "create a plan", or wants structured project planning.
jasonraimondi/dotfiles 18
planning-write-an-issue Create a single issue by interviewing the user, exploring the codebase, and writing a structured YAML issue file. Use when user says "write an issue", "create an issue", "add an issue", or wants to define a single work item — either standalone or inside an existing plan.
jasonraimondi/dotfiles 18
sync-linear-to-plan Pull current state from Linear back into local ./plans/{slug}/ YAML files — updates status, assignee, priority, labels, and points. Also imports new issues created directly in Linear. Use when user says "pull from linear", "sync from linear", "update plan from linear", or wants local files to reflect Linear's current state.
jasonraimondi/dotfiles 18
sync-plan-to-linear Sync a local ./plans/{slug}/ directory to Linear — creates or updates projects, documents, issues, and dependencies. Writes Linear IDs back to local YAML for idempotent re-syncs. Use when user says "sync to linear", "push to linear", "publish plan", or wants to mirror local plan state in Linear.
jasonraimondi/dotfiles 18
testing-tdd Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
jasonraimondi/dotfiles 18
testing-vitest Vitest fast unit testing framework powered by Vite with Jest-compatible API. Use when writing tests, mocking, configuring coverage, or working with test filtering and fixtures.
jasonraimondi/dotfiles 18
tooling-agent-browser Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
jasonraimondi/dotfiles 18
tooling-commit Suggest a conventional commit message for the current staged/unstaged changes. Use when the user asks to commit, wants a commit message, says "commit", or wants to stage and commit code changes.
jasonraimondi/dotfiles 18
tooling-improve-codebase-architecture Explore a codebase to find opportunities for architectural improvement, focusing on making the codebase more testable by deepening shallow modules. Use when user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more AI-navigable.
jasonraimondi/dotfiles 18
tooling-linear-cli Manage Linear issues from the command line using the linear cli. This skill allows automating linear management.
jasonraimondi/dotfiles 18
tooling-pnpm Node.js package manager with strict dependency resolution. Use when running pnpm specific commands, configuring workspaces, or managing dependencies with catalogs, patches, or overrides.
jasonraimondi/dotfiles 18
tools-image-manipulation-image-magick Process and manipulate images using ImageMagick. Supports resizing, format conversion, batch processing, and retrieving image metadata. Use when working with images, creating thumbnails, resizing wallpapers, or performing batch image operations.
jasonraimondi/dotfiles 18
typescript-advanced-types Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications. Use when implementing complex type logic, creating reusable type utilities, or ensuring compile-time type safety in TypeScript projects.
jasonraimondi/dotfiles 18
typescript-better-auth-best-practices Skill for integrating Better Auth - the comprehensive TypeScript authentication framework.
jasonraimondi/dotfiles 18
code-review Code review workflow using GitHub CLI. Use when reviewing pull requests, checking PR diffs, adding review comments, or approving/requesting changes on PRs.
ntsk/dotfiles 3
decision-archaeology Investigate why code was written a certain way. Use when tracing decision history through git blame, commit logs, PRs, and issues to understand the reasoning behind code changes.
ntsk/dotfiles 3
gh-pr This skill should be used when creating a GitHub pull request via `gh pr create`. Defines PR body format with Why/What/Notes sections, ensures proper assignment, and prompts for Jira ticket number.
fredrikaverpil/dotfiles 213
git-commit This skill should be used BEFORE running any git commit command. Triggers when about to run `git commit`. Ensures commit messages follow Conventional Commits specification and prompts for Jira ticket number.
fredrikaverpil/dotfiles 213
golangci-lint When linting is failing.
fredrikaverpil/dotfiles 213
gh-cli GitHub CLI (gh) command reference. Use when working with GitHub repositories, PRs, issues, actions, `gh api`, or any GitHub operations from the command line.
fredrikaverpil/dotfiles 213
gh-pr This skill should be used when creating a GitHub pull request via `gh pr create`. Defines PR body format with Why/What/Notes sections and ensures proper assignment.
fredrikaverpil/dotfiles 213
git-commit This skill should be used BEFORE running any git commit command. Triggers when about to run `git commit`. Ensures commit messages follow Conventional Commits specification.
fredrikaverpil/dotfiles 213
golang-style Use this skill BEFORE writing or editing any Go (.go) files. Triggers when about to create, modify, or add code to .go files. Enforces happy path coding, error wrapping, sentinel errors, godoc-style comments, and `go doc` usage.
fredrikaverpil/dotfiles 213
neovim Interact with the user's running Neovim instance via RPC. Use this skill when you need to execute Lua or Vimscript inside Neovim, query buffer state, send commands, or interact with the Neovim runtime in any way. Triggers when the user asks about their current Neovim session, wants to run something inside Neovim, or when you need to inspect Neovim state (buffers, windows, options, LSP, etc.). Also use when running inside a Neovim terminal and needing to communicate with the parent editor.
fredrikaverpil/dotfiles 213