Skip to content
Back to skills

Git Hub Issus

ASecurity

Local git operations for project management. Use when: (1) creating branches for new features/issues, (2) committing and pushing code, (3) pulling latest changes, (4) managing branches, (5) viewing git log/diff/status, (6) preparing code for merge requests or pull requests. Triggers on: git, branch, commit, push, pull, merge, checkout, diff, log, 分支, 提交, 推送.

  • 11 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 10, 2026
businessjavabashrefactoringgitdocumentation

Security analysis

A100/100

Pro scans all 3 files and shows the line behind each finding

Scanned September 10, 2026

npx -y skills add luokai0/ai-agent-skills-by-luo-kai --skill git-hub-issus --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Git Hub Issus?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Git Hub Issus
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/luokai0-git-hub-issus/badge)](https://www.skillsdirectory.com/skills/luokai0-git-hub-issus)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: git-ops
description: "Local git operations for project management. Use when: (1) creating branches for new features/issues, (2) committing and pushing code, (3) pulling latest changes, (4) managing branches, (5) viewing git log/diff/status, (6) preparing code for merge requests or pull requests. Triggers on: git, branch, commit, push, pull, merge, checkout, diff, log, 分支, 提交, 推送."
---

# 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)

Files in this skill

  • .clawhub/origin.json145 B
  • SKILL.md2 KB
  • _meta.json132 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.