github
npx machina-cli add skill chris-hendrix/claudehub/github --openclawGitHub
Workflow methodology for git and GitHub using GitHub Issues, GitHub PRs, and raw git commands.
Tools
Use these tools for development workflows:
- GitHub Issues - Track tasks, bugs, and features
- GitHub PRs - Code review and merging via draft-first workflow
- Raw git - Local version control and branch management
- gh CLI - GitHub operations from the command line
Workflow Strategy
Follow a draft PR-first approach with squash merging - see references/workflows.md for detailed methodology.
Key principles:
- NEVER commit or push directly to the default branch (main/master) - Always work on feature branches
- Every push creates or updates a draft PR
- Always use squash and merge
- Work in small, focused PRs (Graphite-style)
GitHub Issues
Use GitHub Issues to track tasks, bugs, and features - see references/issues.md for guidelines, templates, and commands.
Branch Naming
Follow consistent branch naming conventions - see references/branches.md for detailed guidelines.
Pull Requests
Follow PR best practices for effective code review - see references/pull-requests.md for detailed guidelines, templates, and commands.
Source
git clone https://github.com/chris-hendrix/claudehub/blob/main/plugins/github/skills/github/SKILL.mdView on GitHub Overview
This skill defines a GitHub-centric workflow using Issues, PRs, and raw git commands. It promotes a draft PR-first approach, squash merges, and Graphite-style development to keep changes small and reviewable while protecting the default branch.
How This Skill Works
Developers create feature branches off main, push changes to draft PRs for feedback, and use squash merges to maintain a clean, linear history. The workflow relies on GitHub Issues, PRs, raw git commands, and gh CLI to manage tasks, branches, and merges according to a draft-first methodology.
When to Use It
- Beginning work on a dedicated feature or bug fix branch
- Opening and iterating on a draft PR to solicit early feedback
- Preparing for merge by using squash to consolidate commits
- Tracking tasks, bugs, and features with GitHub Issues and PRs
- Enforcing Graphite-style practice with small, focused PRs and strict no-direct-push-to-default-branch rules
Quick Start
- Step 1: Create a feature branch from main (git checkout -b feature/your-work).
- Step 2: Make changes, commit with descriptive messages, and push to remote to auto-create/update a draft PR.
- Step 3: After review, squash the commits, merge the PR, and delete the feature branch.
Best Practices
- Never commit or push directly to the default branch (main/master).
- Always work on feature branches with clear, focused commits.
- Create or update a draft PR with each push.
- Prefer squash and merge to keep a concise project history.
- Follow consistent branch naming and PR templates to support reviews
Example Use Cases
- A new feature is developed on a feature/hero-banner branch, with iterative draft PR updates and reviewer feedback.
- A bug fix is pushed as a draft PR, then squash-merged after review to produce a single clean commit.
- Multiple small, Graphite-style PRs are opened for different aspects of a feature rather than one large PR.
- Using the gh CLI to open issues, link PRs, and apply labels during the workflow.
- Branch naming follows established conventions and no commits are pushed to main/master.
