Skip to content

git-hub-issus

Verified

Local git operations for project management. Use when: (1) creating branches for new features/issues, (2) committing and pushing code, (3) pulling latest cha...

159 downloads
$ Add to .claude/skills/

About This Skill

# Git Ops Skill

Local git operations for managing project code.

Branch Naming Convention

For new features/issues, create branches with pattern: ``` feature/issue-{number}-{brief-description} ```

For bug fixes: ``` fix/issue-{number}-{brief-description} ```

Standard Workflow

Start new feature from an issue

```bash cd /path/to/project git checkout main git pull origin main git checkout -b feature/issue-1-add-dark-mode ```

After coding is done

```bash git add -A git commit -m "feat: add dark mode support (closes #1)" git push -u origin feature/issue-1-add-dark-mode ```

Create PR/MR after push

  • GitHub: use `github` skill → `gh pr create`
  • GitLab: use `gitlab-ops` skill → `glab mr create`

Common Commands

```bash # Status git status git log --oneline -10 git diff git diff --staged

# Branch management git branch -a git checkout main git checkout -b feature/xxx git branch -d old-branch

# Sync git pull origin main git fetch --all git rebase main

# Stash git stash git stash pop git stash list ```

Known Project Paths

| Project | Path | Remote | |---------|------|--------| | yeahmobiEverything | /Users/zhujinqi/Documents/javacode/learn/yeahmobiEverything | GitHub (zhulaoqi) | | ad-pex-ai | TBD | GitLab (ad-pex/ad-pex-ai) |

Commit Message Convention

  • Use conventional commits:
  • `feat:` new feature
  • `fix:` bug fix
  • `refactor:` code refactoring
  • `style:` UI/style changes
  • `docs:` documentation
  • `chore:` maintenance

Notes

  • Always pull latest before creating new branches
  • Never force push to main/master
  • Ask user before any destructive operations (reset --hard, force push)

Use Cases

  • Create properly named feature and bugfix branches from GitHub issues
  • Follow a standard commit-push-PR workflow for issue-driven development
  • Manage multiple project repositories with consistent branch naming conventions
  • Sync local branches with remote repositories and keep code up to date
  • Generate conventional commit messages linked to issue numbers

Pros & Cons

Pros

  • +Compatible with multiple platforms including claude-code, openclaw
  • +Well-documented with detailed usage instructions and examples
  • +Open source with permissive licensing for commercial use

Cons

  • -No built-in analytics or usage metrics dashboard
  • -Configuration may require familiarity with git & version control concepts

FAQ

What does git-hub-issus do?
Local git operations for project management. Use when: (1) creating branches for new features/issues, (2) committing and pushing code, (3) pulling latest cha...
What platforms support git-hub-issus?
git-hub-issus is available on Claude Code, OpenClaw.
What are the use cases for git-hub-issus?
Create properly named feature and bugfix branches from GitHub issues. Follow a standard commit-push-PR workflow for issue-driven development. Manage multiple project repositories with consistent branch naming conventions.

100+ free AI tools

Writing, PDF, image, and developer tools — all in your browser.

Next Step

Use the skill detail page to evaluate fit and install steps. For a direct browser workflow, move into a focused tool route instead of staying in broader support surfaces.