git-hub-issus

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

Security Scan

This is an instruction-only Git helper consistent with its stated purpose; it requests no credentials or installs and contains only local git commands, though it includes a few minor inconsistencies and exposures you should be aware of.

Purpose & Capability

The skill's name, description, and instructions all describe local Git operations and the provided commands match that purpose. Minor mismatch: the skill does not declare that the git binary is required even though all runtime examples assume git is available.

Instruction Scope

Instructions are limited to common git commands and branch/commit workflow. Two items to note: (1) the SKILL.md contains hard-coded local project paths and a GitHub username (possible PII or environment-specific data) which are informational but could confuse an agent into operating on those paths; (2) the instructions tell the agent to run potentially destructive commands (e.g., rebase, reset, force push guidance) but do explicitly advise asking the user before destructive operations.

Install Mechanism

No install spec and no code files — lowest-risk delivery. Nothing will be written to disk by the skill itself.

Credentials

The skill requests no environment variables or credentials. This is proportionate to a local git operations helper. Note: the SKILL.md references other skills (github, gitlab-ops) which, if used, may require separate credentials.

Persistence & Privilege

The skill is not always-enabled and does not request system or cross-skill configuration changes. Normal autonomous invocation is allowed (platform default) but not escalated by this skill.

Assessment

This skill is an instruction-only Git helper and is internally coherent, but review the following before installing or invoking it: (1) Ensure git is available on your system — the SKILL.md assumes git but the skill doesn't declare it as required. (2) The file lists specific local project paths and a GitHub username — verify these aren't sensitive for you and be cautious that an agent executing commands could operate on local repositories. (3) The skill references potentially destructive commands (rebase, reset, force-push); the document says to ask first, so require explicit confirmation before allowing the skill or agent to run such commands. (4) If you plan to use the referenced github/gitlab skills for PR/MR creation, those other skills will likely need credentials — check their requirements separately. If you want stricter safety, only invoke this skill interactively (not autonomously) and review any generated commands before execution.

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

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

After coding is done

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

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