← all publishers

fredrikaverpil

@fredrikaverpil source repo

Report this profile Claim this profile

• 19 skills
• 0 followers
• 9 hours ago last updated

1. ▌
   Obsidian 2 · fredrikaverpil

   Find, navigate, read, and edit notes in the user's personal Obsidian vault (an iCloud-synced markdown collection on macOS). Use whenever the user mentions "the vault", "my notes", "Obsidian", a daily note, a meeting note, scratchpad, or asks to look up/jot down something that sounds personal-knowledge-base-like (e.g. "what did I write about X", "add a note about Y", "today's daily note") — even if they don't say the word "Obsidian".
   0
   installs
2. ▌
   Pr Style 2 · fredrikaverpil

   This skill should be used when creating or editing a GitHub pull request title or description, regardless of tool (gh CLI, GitHub MCP tools, API). Defines PR title format and body format with Why/What/Notes sections, and prompts for the Jira ticket number.
   0
   installs
3. ▌
   Git Commit 2 · fredrikaverpil

   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 the Jira ticket number.
   0
   installs
4. ▌
   Aip · fredrikaverpil

   Google API Improvement Proposals (AIP) reference. Use BEFORE designing or reviewing APIs, protobuf definitions, or any work involving Google API design standards. Fetches relevant AIP rules from https://google.aip.dev for the task at hand.
   0
   installs
5. ▌
   Gh Pr · fredrikaverpil

   This skill should be used when creating a GitHub pull request via `gh pr create`. Covers the gh CLI mechanics; PR title and body conventions come from the pr-style skill.
   0
   installs
6. ▌
   Smart · fredrikaverpil

   Run a task through a budget-aware multi-model pipeline from one main chat that never switches model: plan and interview, orchestrate implementer subagents, then review. Use when you want planning, implementation, and review handled by different models.
   0
   installs
7. ▌
   Gh CLI · fredrikaverpil

   GitHub CLI (gh) conventions and the inline PR review recipe. Use when working with GitHub repositories, PRs, issues, actions, `gh api`, or any GitHub operations from the command line.
   0
   installs
8. ▌
   Neovim · fredrikaverpil

   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.
   0
   installs
9. ▌
   Obsidian · fredrikaverpil

   Find, navigate, read, and edit notes in the user's personal Obsidian vault (an iCloud-synced markdown collection on macOS). Use whenever the user mentions "the vault", "my notes", "Obsidian", a daily note, a meeting note, scratchpad, or asks to look up/jot down something that sounds personal-knowledge-base-like (e.g. "what did I write about X", "add a note about Y", "today's daily note") — even if they don't say the word "Obsidian".
   0
   installs
10. ▌
    Pr Style · fredrikaverpil

    This skill should be used when creating or editing a GitHub pull request title or description, regardless of tool (gh CLI, GitHub MCP tools, API). Defines PR title format and body format with Why/What/Notes sections.
    0
    installs
11. ▌
    Git Commit · fredrikaverpil

    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.
    0
    installs
12. ▌
    Nvim Config · fredrikaverpil bundle

    Native Neovim config idioms and conventions — use whenever writing, reviewing, or modifying any Neovim configuration that uses Neovim's built-in conventions WITHOUT a plugin manager framework (no lazy.nvim, packer, etc.). Covers directory structure, vim.pack plugin management, lsp/ auto-discovery, plugin/ loading order, keymaps, and standard paths. Trigger on any task involving init.lua, plugin/*.lua, lsp/*.lua, vim.pack.add(), vim.lsp.enable(), or "native neovim config" — even if the user just says "add a plugin" or "configure LSP" in a native-style config.
    0
    installs
13. ▌
    Nvim Plugin · fredrikaverpil

    Conventions and tooling for authoring a Neovim plugin in Lua. Use when creating, modifying, or reviewing a plugin — plugin structure, ftplugin, health checks, `setup()`, vimdoc, LuaCATS, lazy loading — or when working in a directory that looks like one (plugin/, lua/, ftplugin/).
    0
    installs
14. ▌
    Self Review · fredrikaverpil

    Deliberate end-to-end review pass over a completed change, applying the laziness ladder. Invoke when the user asks for a review, or when orchestrating one. Not a routine step after every edit.
    0
    installs
15. ▌
    Golang Style · fredrikaverpil

    Go conventions specific to this author. Use before writing or editing any Go (.go) file.
    0
    installs
16. ▌
    Codebase Audit · fredrikaverpil

    Analyze a git repo's history to surface high-churn files, ownership risks, bug hotspots, momentum trends, and firefighting patterns. Use this skill whenever the user wants to understand a codebase, assess repo health, or orient themselves before reading code — even if they don't explicitly say "audit". Examples: "audit this repo", "analyze this repo's history", "what's the state of this codebase?", "bus factor", "churn analysis", "tell me about this repo", "who owns this code?", "is this repo healthy?".
    0
    installs
17. ▌
    Plan Interview · fredrikaverpil

    Before creating a plan, interview the user
    0
    installs
18. ▌
    Nix Install · fredrikaverpil

    Install Nix in the Claude Code web sandbox (the cloud environment) as a general-purpose package installer, then install packages from the Nix binary cache with no GitHub access. Use whenever a web session needs a tool that isn't preinstalled and isn't in a language registry (npm/pypi/crates/go) — Neovim, ripgrep, a compiler, anything in nixpkgs. Installs nix-bin via apt, configures single-user mode, and installs packages via nix-env against the nixpkgs channel tarball. Web-sandbox only.
    0
    installs
19. ▌
    Nvim Install · fredrikaverpil

    Install Neovim and stand up the nvim-fredrik config in the Claude Code web sandbox (the cloud environment), where no Neovim exists. Use this before testing any Neovim config change in a web session, e.g. checking out a PR branch that touches nvim-fredrik and observing its runtime behavior. Installs Neovim via Nix from the binary cache with no GitHub access, wires the repo's config into place, launches Neovim headless with a listen socket, and exports $NVIM so the `neovim` RPC skill can drive it. Web-sandbox only.
    0
    installs