All authors

Claude Skills by fredrikaverpil
github.com/fredrikaverpil25 skills0 installs70 views
- AipGoogle 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.Votes: 0GitHub stars: 260
- Codebase AuditAnalyze 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".Votes: 0GitHub stars: 260
- Gh CliGitHub CLI (gh) command reference. Use when working with GitHub repositories, PRs, issues, actions, `gh api`, or any GitHub operations from the command line.Votes: 0GitHub stars: 260
- Gh PrThis 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.Votes: 0GitHub stars: 260
- Git CommitThis 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.Votes: 0GitHub stars: 260
- NeovimInteract 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.Votes: 0GitHub stars: 260
- ObsidianThe user keeps a personal Obsidian vault as plain markdown files synced via iCloud. The vault is just a directory tree, so all standard Unix tools work — no Obsidian app required to read or write notes.Votes: 0GitHub stars: 260
- Plan InterviewBefore creating a plan, interview the userVotes: 0GitHub stars: 260
- ProofProvide proof to your claim(s)Votes: 0GitHub stars: 260
- Self ReviewWhen done with implementation, perform self-review of the workVotes: 0GitHub stars: 260
- Golang StyleTry to follow the proverbs:Votes: 0GitHub stars: 260
- Nvim ConfigNative 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 ju...Votes: 0GitHub stars: 260
- Nvim PluginReference: https://neovim.io/doc/user/lua-plugin/Votes: 0GitHub stars: 260
- Nix InstallInstall 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.Votes: 0GitHub stars: 260
- Nvim InstallInstall 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 ...Votes: 0GitHub stars: 260
- Pr StyleThis 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.Votes: 0GitHub stars: 260
- SmartThree phases from a single main chat on the smart model. The point is to keep expensive tokens on the judgment work — planning, verifying, reviewing — and delegate implementation and research to subagents carrying their own cheaper, pinned model. Hub-and-spoke, not a team: workers report to the orchestrator and never talk to each other, so [subagents](https://code.claude.com/docs/en/sub-agents) fit and [agent teams](https://code.claude.com/docs/en/agent-teams) don't. Leave `CLAUDE_CODE_EXPERI...Votes: 0GitHub stars: 260
- AipGoogle 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.Votes: 0GitHub stars: 260
- Codebase AuditAnalyze 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...Votes: 0GitHub stars: 260
- Gh CliGitHub 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.Votes: 0GitHub stars: 260
- Gh PrThis 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.Votes: 0GitHub stars: 260
- Git CommitThis skill should be used BEFORE running any git commit command. Triggers when about to run `git commit`. Ensures commit messages follow Conventional Commits specification.Votes: 0GitHub stars: 260
- ObsidianThe user keeps a personal Obsidian vault as plain markdown files synced via iCloud. The vault is just a directory tree, so all standard Unix tools work — no Obsidian app required to read or write notes.Votes: 0GitHub stars: 260
- Pr StyleThis 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.Votes: 0GitHub stars: 260
- Self ReviewDeliberate 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.Votes: 0GitHub stars: 260