Menu
SkillsMP has collected 28 skills from carlos-algms/dotfiles. Open a skill to review its source and details.
Showing 28 of 28 collected skills.
Use when a `discussion_rNNN` URL anchor appears, when replying to a specific PR review comment from a bot or AI reviewer (CodeRabbit, cubic, Claude, Copilot) or a human reviewer, reading all reviews on a PR with their replies as a tree, or resolving review…
Execute and orchestrate multiple AI agent CLIs (agy, Codex, Cursor, Claude Code, Pi) for getting alternative opinions, comparing approaches, or leveraging different AI models' strengths. Use when the user explicitly mentions agent names like "ask agy", "ask…
Compose and create GitHub pull requests with `gh` using the target repository's title, template, base-branch, and draft conventions. Load on explicit user intent to open, create, draft, or compose a pull request.
Compose repository-compatible Git commit messages and exact commit commands from current repository state. Load on intent to commit, stage, compose a commit message, prepare a PR title, or edit `.git/COMMIT_EDITMSG`.
Create a written implementation plan saved to a file. Use only when the user directly invokes the writing-plans skill or explicitly asks for a written plan. Do not use for in-memory plans, in-chat plans, internal task decomposition, native task lists, or…
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Create or update a terse milestone file composed of delegated implementation plans. Use only when the user directly invokes milestone-planner or explicitly asks to create or update a milestone plan. Do not infer use from large features, multiple plans,…
Subagent-per-task MODE of executing-plans. Requires executing-plans, which holds the shared rules; load that first if it is not already loaded.
Extract clean markdown content from web pages using Defuddle CLI, removing clutter and navigation to save tokens. Use instead of WebFetch when the user provides a URL to read or analyze, for online documentation, articles, blog posts, or any standard web…
Use for ad-hoc code review: after a major feature, before merging to main, or when stuck. Executing a written plan instead? Use executing-plans, which owns the per-task review cycle.
Use when about to claim work is complete, fixed, or passing, before committing, pushing, or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
Interview the user about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
Fast, MVP-focused grilling session for plans, prototypes, designs, or feature ideas. Use when the user wants to stress-test direction, clarify assumptions, reduce scope, or get challenged without a long decision-tree interview.
Summarize a video (URL or local path) by pulling captions first, falling back to audio-only transcription, and optionally extracting frames for visual summaries. Use when the user pastes a YouTube/Vimeo/X/etc URL, points at a local video file, or asks to…
Multi-provider web search fanout across Exa, Tavily, Brave, LangSearch, and Marginalia with parallel dispatch, dedupe, and AI summary. Use ONLY on explicit user intent for a named provider (Exa, Tavily, Brave, LangSearch, Marginalia), cross-provider fanout,…
Load before any Jira interaction or mcp__atlassian__* call. Holds required field values (team ID, sprint IDs, custom field mappings) unavailable elsewhere; skipping causes missing fields on created tickets. Triggers: Jira URLs, ticket keys (e.g. ABC-123), MCP…
Simplify and reduce code while preserving behavior. Use when the user asks to simplify, clean up, refactor, audit, report on, or reduce recently changed code. Supports apply mode for edits and report mode for findings only.
Review current branch changes against a target branch. Use when the user asks to review a branch, review changed files, compare current work to main, origin HEAD, or master, or run a file-by-file code review with aggregated markdown results.
Simplify and reduce tests while preserving coverage. Use when the user asks to simplify, deduplicate, reduce, or clean up test files using techniques such as equivalence class partitioning, decision tables, or pairwise testing.
Personal Obsidian CLI mechanics and patterns not covered by the base `obsidian-cli` skill. Load when driving the Obsidian CLI for content creation, file operations, vault hygiene, or version history. Triggers on: "search my vault", "find notes about", "show…
Durable repo-specific notes: project findings, investigations, decisions, coding lessons, failure analyses, and implementation findings. Distinct from the agent's native memory feature. Triggers: "save to project notes", "project notes", "save this to my…
Second-brain long-term wiki notes and personal documentation. High-priority over generic Obsidian skills for vault content routing. Load this first when the user asks to search, read, create, update, move, or organize notes in their vault. Routes reusable…
Rules for creating new git branches - naming and workflow. Load on intent to start a branch. Triggers: "new branch", "create branch", "checkout -b", "switch -c", "start branch", "branch off", or Jira ticket as starting point.
Enforces strict CSS and CSS Modules policies for ALL CSS authoring, including stylesheet files (.css/.scss/.module.css) and CSS-in-JS (styled-components, Emotion, vanilla-extract, styled-jsx, Stitches, template literal styles embedded in TS/JS files). Use…
Writes unit tests for JavaScript/TypeScript and frontend projects using Vitest or Jest. Use when writing or running tests.
Load before any Neovim help, documentation, or Lua API lookup. Defines how to read Neovim docs from disk or online. Reading docs via `nvim --headless` or any other `nvim` subprocess is FORBIDDEN; Triggers: "Neovim docs", `:help`, `:h <topic>`, `runtime/doc`,…
Writes React components and hooks using TypeScript. Use when creating or modifying React components, hooks, or JSX.
Enforces strict TypeScript and JavaScript style policies for ALL .ts/.tsx/.js/.jsx file operations. Use when creating, writing, or editing ANY TS/JS code. Triggers include: components, hooks, services, utilities, classes, interfaces, types, schemas, tests,…