creating-pull-requests
Creating & Updating Pull Requests
Create well-structured pull requests, or update existing ones to reflect the current state of the branch.
Critical Rules
NEVER do these:
- Do NOT add yourself as a coauthor on commits (no
Co-Authored-Byheaders) - Do NOT include phrases like "Generated with Claude Code" or "Created by Claude"
- Do NOT mention AI or Claude anywhere in commits or PR descriptions
PR Title Format
Use active voice with a present-tense verb:
More from tdhopper/dotfiles2.0
stop-slop
Use this skill when writing or editing prose to eliminate predictable AI writing patterns. Helps make writing more direct, authentic, and human.
9commit
Use this skill when creating a git commit
8reviewing-code
Review pull requests, branch changes, or code diffs. Triggers on "review this PR", "review my changes", "code review", "review branch", or GitHub PR URLs. Focuses on bugs, tests, complexity, and performance - not linting.
8managing-dotfiles
Use this skill when working with personal dotfiles managed by yadm. This includes pulling remote changes, committing and pushing dotfile changes, modifying configuration files (shell, editor, terminal, git, etc.), viewing tracked files, resolving merge conflicts, and maintaining the dotfiles repository. For work dotfiles, use the managing-work-dotfiles skill instead.
8managing-work-dotfiles
Use this skill when working with work-specific dotfiles managed by yadm-work. This includes pulling remote changes, committing and pushing work dotfile changes, modifying work configuration files, viewing tracked work files, resolving merge conflicts, and maintaining the work dotfiles repository at Spotify GHE. Triggers on "work dotfiles", "yadm-work", "spotify dotfiles", or work-related config management.
4add-knowledge
Add notes and learnings to Tim's work knowledge base at Spotify from any Claude Code session
3