negz
@negz
Public Skills
writing-style
by negz
Write documents in Nic Cope's voice and style. Use when drafting designs, one-pagers, PRDs, proposals, explorations, blog posts, or any prose document. Also use when the user asks to draft, write, or author a document, or asks you to capture their thoughts in writing.
scratch-docs
by negz
Draft, publish, and iterate on markdown documents in the upbound/scratch repo. Use when the user wants to draft a document (PRD, design, exploration, R&D notes), open a PR for review, read review comments, or iterate on a scratch document. Also use when the user mentions their scratch repo.
git-commits
by negz
Write git commits in Nic Cope's style. Use when creating commits, staging changes for commit, or when the user asks to commit. Includes Signed-off-by requirements and problem-first messaging.
github-issues
by negz
Create GitHub issues in Nic Cope's style. Use when opening, creating, or filing issues, bug reports, feature requests, or proposals. Uses gh CLI and respects issue templates.
github-pull-requests
by negz
Create and manage GitHub pull requests in Nic Cope's style. Use when creating, opening, or drafting PRs, or updating PR descriptions. Uses gh CLI.
github
by negz
Interact with GitHub using the gh CLI. Use when viewing PRs, checking CI status, reviewing code, listing issues, or any GitHub operation. Prefer gh over web fetching.
go-code-factoring
by negz
Factor and structure Go code for clarity, testability, and composability. Use when writing new Go code, refactoring existing code, reviewing code structure, adding interfaces, decomposing large functions or structs, or when the user mentions factoring, refactoring, architecture, or code organization. Also use before writing unit tests to ensure code is well structured.
go-unit-tests
by negz
Write unit tests for Go code. Use when creating, adding, or updating Go tests, writing table-driven tests, creating mocks or fakes, adding test coverage, or when the user mentions testing, cmp.Diff, assertions, or test cases. Also use when reviewing whether code is testable.
nix-flake
by negz
Develop projects that use a Nix flake. Use when building, testing, linting, running dev commands, or entering a dev shell for a project that has a flake.nix. NOT for running ad-hoc CLI tools - use nix-tools for that.
nix-tools
by negz
Run any CLI tool via Nix - assume tools like jq, yq, ripgrep, and fd are available. Use CLI tools freely for JSON/YAML processing and searching. Also use when a command is not found.
skill-creator
by negz
Create new skills, modify and improve existing skills. Use when users want to create a skill from scratch, turn a workflow into a skill, update or optimize an existing skill, improve a skill's description for better triggering accuracy, or when they mention SKILL.md files.