github-operations

Guides Git branching, commit conventions, pull requests, and GitHub workflow configuration.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/JenilRevaliya/ARGUS --skill github-operations-jenilrevaliya
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-operations
Source: https://github.com/JenilRevaliya/ARGUS/tree/main/.agent/skills/github-operations
Command: npx skills add https://github.com/JenilRevaliya/ARGUS --skill github-operations-jenilrevaliya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams struggle with inconsistent commit histories, messy pull requests, merge conflicts, and unclear branching strategies, leading to broken main branches and slow code review cycles. ## Core Features & Use Cases - Branching Strategies: Provides decision guidance between trunk-based development and Git Flow, with rules for branch lifetime, merging, and deployment. - Commit & PR Standards: Enforces Conventional Commits format, breaking change notation, and structured pull request templates with review checklists. - Git Operations Reference: Covers interactive rebase, merge conflict resolution, stashing, and safe undo patterns including reflog recovery. - Repository Hardening: Documents branch protection rules, Git hooks with Husky and lint-staged, and commitlint configuration. - Use Case: A developer about to merge a feature branch can follow the rebase and conflict resolution steps, write a compliant commit message, and open a PR that passes branch protection checks. ## Quick Start Ask the assistant to help clean up your local commits with an interactive rebase and write a conventional commit message before opening a pull request.

Frequently Asked Questions about github-operations

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a conventional commit message?▼

Use the format type(scope): description, where type is one of feat, fix, docs, style, refactor, perf, test, chore, or ci. Add an optional body explaining why the change was made, and mark breaking changes with an exclamation mark and a BREAKING CHANGE footer.

How to resolve Git merge conflicts during a rebase?▼

Run git fetch origin then git rebase origin/main, open conflicted files, and edit the sections marked with conflict markers. Stage resolved files with git add, continue with git rebase --continue, or abort entirely with git rebase --abort.

Trunk-based development vs Git Flow, which should I use?▼

Use trunk-based development when main must always be deployable and feature branches live under two days. Use Git Flow for versioned releases like mobile apps or libraries with multiple environments and long-lived feature development.

Is it safe to rebase commits that are already pushed?▼

No, rebasing pushed commits rewrites history and requires a force push, which breaks other collaborators' branches. Only rebase local, unpushed commits; use git revert to undo shared commits safely.

How do I recover a deleted Git branch?▼

Run git reflog to find the commit hash where the branch pointed, then recreate it with git checkout -b branch-name followed by the commit hash. The reflog tracks HEAD movements even after branch deletion.

How to set up pre-commit hooks with Husky and lint-staged?▼

Add a prepare script running husky in package.json, configure lint-staged to run eslint and prettier on staged files, and create a .husky/pre-commit hook executing npx lint-staged. Add commitlint in a commit-msg hook to enforce message conventions.