organizing-github
Conventions for GitHub repo locations, forks, and open source contribution boundaries.
Script and automate repetitive tasks and workflows.
Conventions for GitHub repo locations, forks, and open source contribution boundaries.
Systematically fetch, analyze, and fix code review issues from GitHub Pull Requests. Use when the user asks to review and fix code issues from AI code reviewers (like Gemini Code Assist, GitHub Copilot, CodeRabbit) or any PR review comments. Fetches all review comments using gh CLI, attempts to fix all reported issues, commits changes to the PR branch, and generates a comprehensive fix report. Triggers on requests like "fix PR review issues", "address code review feedback", "apply review suggestions", or when given a GitHub PR URL with review comments to address.
Manages git worktrees including listing, creating, removing, and switching between worktrees. Use when the user mentions creating worktrees, create a work tree, create worktree, new worktrees, parallel branches, or working on multiple branches simultaneously.
Generate descriptive commit messages by analyzing git diffs. Use when the user asks for help writing commit messages or reviewing staged changes.
Generate clear, conventional commit messages following project rules. Use when creating commits, writing commit messages, or reviewing staged changes.
Project structure and coding conventions for RawDrive. Use when creating new files, organizing code, or understanding the codebase layout. CRITICAL for preventing random file creation.
Create, amend, and manage Git commits with gh CLI including status checks and commit message validation
Iteratively, commit atomic changes to the respository. Use when the user or agent needs to autonomously commit atomic changes to the repository. Employs the "git-add", "git-message", and "git-status" in skills in sequence to perform the commit.
Use for investigation-heavy work. Prefer tool-driven evidence (search, logs, diffs) before changing code.
Use when creating git commits or pull requests. Enforces conventional commit format and atomic change principles. Verified on Git 2.30+
Apply when committing code, creating branches, or preparing pull requests. Covers conventional commit format, branch naming, co-author attribution, and pre-commit checklist.
Review committed changes and create a pull request on GitHub. Use when the user wants to create a PR, requests pull request creation, or asks to open changes for review. Supports --japanese flag for Japanese PR descriptions, --base flag to specify target branch, and --update flag to update existing PR. Works with GitHub repositories using the github MCP server.
Creates git commits following project-specific conventional commit conventions for a Quartz blog (content, fix, style, build prefixes)
Generate conventional commit messages following git-cz style by default (emoji between type and subject). Automatically detects project configuration when present. Use when creating git commit messages with Conventional Commits specification. See references/config-detection.md for supported configurations.
Create well-structured git commits with conventional commit messages. Use when user wants to commit changes or asks about commit best practices.
Generate descriptive commit messages by analyzing git diffs. Use when the user asks for help writing commit messages or reviewing staged changes.
[PROJECT] file and directory structure conventions and enforcement
Writes and verifies GitHub pull request descriptions with zero fabrication tolerance. Discovers project PR templates, generates descriptions from git changes, and applies technical documentation verification standards. Use when creating PR descriptions (automatically invoked by create-pr skill), verifying PR descriptions, updating PR descriptions after additional changes, discovering templates, or when user requests "write PR description" or "verify PR description".