pr-review-from-comments
Converts "AI" comments in local files into Github PR review comments
Converts "AI" comments in local files into Github PR review comments
Use when needing to check PR review comments on current branch, before addressing reviewer feedback, or when asked to fetch/review PR comments
Git expert covering branching strategies, collaboration, conflict resolution, and best practices
This skill should be used when creating commits or pull requests, enforcing a human-written PR structure, intent capture, and evidence in agentic workflows.
Create GitHub issues (feature requests or bug reports) by learning from existing issue formats in the repository.
Validates branch is ready for merge with step-by-step checklist. Use when user asks "is everything ready for merge?", "ready to merge?", "can I merge?", "merge checklist", or "pr ready?".
Use this skill when any task is complete, before beginning any non-trivial task, or whenever working with git or tasked with commiting code.
Deep knowledge expert for the 33GOD agentic pipeline system, understands component relationships and suggests feature implementations based on actual codebase state
Use when creating or developing anything, before writing code or implementation plans - refines rough ideas into fully-formed designs through structured Socratic questioning, alternative exploration, and incremental validation. Optimized for git worktree workflows and Claude CLI agent patterns.
Use for any development work - the master 13-step coding process that orchestrates all other skills, ensuring GitHub issue tracking, proper branching, TDD, code review, and CI verification
DevOps expert for building robust CI/CD pipelines with GitHub Actions, GitLab CI, Jenkins
Use when encountering merge conflicts - handle conflicts cleanly, verify resolution, and maintain code integrity
Use when creating a pull request or preparing changes for review. Ensures PR titles and descriptions accurately reflect ALL changes in the branch AND link to related GitHub issues. Prevents accidentally omitting files, changes, or issue references from PR descriptions.
Use to keep GitHub Project fields synchronized with actual work state - updates status, verification, criteria counts, and other project-specific fields
Use when updating specifications, comparing branches, or ensuring documentation reflects current implementation.
Use during all development - no TODOs, no FIXMEs, no "we'll add this later"; do it now or get explicit deferral permission
Use after completing implementation - create pull request with complete documentation, proper labels, linked issues, and verification summary
Techniques for diagnosing and recovering from corrupted git state, orphaned worktrees, and inconsistent branch references.
Create properly named feature branch from development with remote tracking, following WescoBar naming conventions and git best practices
Manage skills from local paths or git repositories - add, update, or remove skill tips in ~/.claude/skills with group-skillname format
This skill should be used when the user asks to "download files from GitHub", "fetch a folder from a repo", "grab code from GitHub", "download a GitHub repository", "get files from a GitHub URL", "clone just a folder", or needs to download specific files/folders from GitHub without cloning the entire repo.
Use before starting ANY work - hard gate ensuring a GitHub issue exists, creating one if needed through user questioning
Expertise in Go programming decisions according to the Google Go Style Guide. Focuses on specific choices for naming, error handling, and language usage.