Skip to content
Skills Library
Programming · Automation

github-use

/github-use

Any time github or git activity is required, including committing and pushing changes, creating or switching branches, merging, creating issues, checking status or logs, or reverting commits. Trigger whenever the user says "update", "commit", "push", "merge", "create branch", "checkout", "create issue", "git status", "revert", or any git/GitHub-related request - even if not framed explicitly as a "GitHub task." Load with read_file on .kilocode/skills/github-use/SKILL.md (ignore the absolute path in the location tag).

Licence
CC0-1.0
Last repository change
22.06.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 22.06.2026, without references to retired models or APIs.

Licence

CC0-1.0, otwarta.

What it does and when to use it

Any time github or git activity is required, including committing and pushing changes, creating or switching branches, merging, creating issues, checking status or logs, or reverting commits. Trigger whenever the user says "update", "commit", "push", "merge", "create branch", "checkout", "create issue", "git status", "revert", or any git/GitHub-related request - even if not framed explicitly as a "GitHub task." Load with read_file on .kilocode/skills/github-use/SKILL.md (ignore the absolute path in the location tag).

Triggers from the description

updatecommitpushmergecreate branchcheckoutcreate issuegit status
Original author description

Any time github or git activity is required, including committing and pushing changes, creating or switching branches, merging, creating issues, checking status or logs, or reverting commits. Trigger whenever the user says "update", "commit", "push", "merge", "create branch", "checkout", "create issue", "git status", "revert", or any git/GitHub-related request - even if not framed explicitly as a "GitHub task." Load with read_file on .kilocode/skills/github-use/SKILL.md (ignore the absolute path in the location tag).

How it works

  1. Update
  2. Create branch
  3. Checkout branch
  4. List branches
  5. Create issue
  6. Revert
  7. Merge to main
  8. Status
  9. Log
  10. Branch
Original SKILL.md headings · 134 lines, 1,068 words
SKILL.md preview
---
name: github-use
description: Any time github or git activity is required, including committing and pushing changes, creating or switching branches, merging, creating issues, checking status or logs, or reverting commits. Trigger whenever the user says "update", "commit", "push", "merge", "create branch", "checkout", "create issue", "git status", "revert", or any git/GitHub-related request - even if not framed explicitly as a "GitHub task." Load with read_file on .kilocode/skills/github-use/SKILL.md (ignore the absolute path in the location tag).
---

# Command index
- **update**: Stage, commit, and push all changes. See "## Update".
- **merge to main**: Merge current branch into main. See "## Merge to main".
- **create issue**: Create a new GitHub issue. See "## Create issue".
- **create branch**: Create a new branch from current branch and switch to it. See "## Create branch".
- **checkout branch**: Switch to an existing branch. See "## Checkout branch".
- **list branches**: List all branches. See "## List branches".
- **revert**: Revert a specific commit by hash. See "## Revert".
- **status**: Show working tree state. See "## Status".
- **log**: Show recent commit history. See "## Log".
- **branch**: Show current branch name. See "## Branch".

# Environment
- Read skill-local guidance only when `.kilocode/skills/github-use/AGENTS.md` is confirmed to exist; otherwise use root `AGENTS.md` for project-specific shell, virtualenv, and credential guidance.

# Response style
- Skip narration ("Now I will…"). Just act and report at the end.
- **Success**: One summary line + key details (branch, commit hash, sync status).
- **Failure**: One summary line + key error snippet + one or two concrete next steps.

> Example success: `Update complete: 3 files committed on branch feature/x, pushed to origin/feature/x; local and remote are in sync.`

# General rules (all workflows)

**Error handling**: Stop at the first error, capture the output, and give the user troubleshooting options rather than continuing blindly.

**Authority**: Run all git commands without asking permission. Just execute and report.

**Prohibited**:
- No `git push --force` or `--force-with-lease` on main.
- No `git rebase` on main.

**Remote**: Default to `origin` unless the user specifies otherwise.

**Command chaining**: Run each git command separately - never chain with `;` or `&&`.

**Backticks in commit messages**: Avoid backticks in commit message text because some shells treat them as escape or substitution characters. Write identifiers as plain text.

# Command workflows

## Update
Stage, commit, and push all changes to the remote.

1. **Status check**: `git status` - see all modified, untracked, and staged files.
2. **Research changes**: Understand *what* changed and *why*, not just which files changed. Use `codebase_search`, `read_file`, or `search_files` as needed. A meaningful commit message describes the work, not just the filenames.
3. **Stage all changes**: `git add -A` (handle special cases as needed).
4. **Craft commit message**:
   - Concise subject line.
   - Short but complete body: what was done and why.
   - List affected file paths.
   - No backticks.
   - No carriage returns or line feeds within the message. Enclose the full message in quotes as a single `-m` argument.
      **Wrong** (has line feeds or carriage returns):
      ```
      git commit -m "Fix...

      - An item that was changed...
      - Another item that was changed...

      Files: file.py, another_file.py"
      ```

      **Right** (no line feeds or carriage returns):
      ```
      git commit -m "Fix...: (1) An item that was changed... (2) Another item that was changed... Files: file.py, another_file.py"
      ```
5. **Commit**: `git commit -m "[message]"` - no permission needed, just run it.
6. **Verify**: Confirm commit succeeded and note the hash.
7. **Push**: `git push origin <branch>`. If credentials are requested, follow the project's credential guidance.
8. **Confirm sync**: Verify local and remote are in sync.

## Create branch
Create a new branch and switch to it.

1. **Branch name**: If not provided, stop and ask. Prefer `feature/<short-name>` or `fix/<short-name>`.
2. **Current state**: `git branch --show-current` then `git status -sb`. Note any uncommitted changes - they carry over to the new branch.
3. **Validate name**: `git check-ref-format --branch "<branch_name>"`. If invalid, stop and tell the user why.
4. **Existence check**: Confirm the branch doesn't already exist locally. If it does, suggest the **checkout branch** workflow.
5. **Create and switch**: `git switch -c <branch_name>`.
6. **Verify**: Confirm the active branch is now the new one.

## Checkout branch
Switch to an existing branch.

1. **Branch name**: If not provided, stop and ask (or show available branches with `git branch -a` first).
2. **Dirty check**: `git status -sb` - if uncommitted changes exist, warn the user they won't automatically carry over. Do not auto-stash; let the user decide.
3. **Switch**: `git switch <branch_name>`.
4. **Verify**: Confirm the active branch is the requested one.

## List branches
1. `git branch -a` - shows all local and remote-tracking branches.
2. Clearly indicate which branch is currently active.

## Create issue
Create a GitHub issue using the `gh` CLI.

1. **Collect info**: If title or body is missing, ask for them before proceeding.
2. **Create**: `gh issue create --title "<title>" --body "<body>"`.
   - If `gh` is not installed or not authenticated, stop and report that to the user.
3. **Confirm**: Share the new issue URL.

## Revert
Revert a specific commit by creating a new undo commit - history is preserved, nothing is deleted.

1. **Confirm hash**: If not provided, show `git log --oneline -n 10` to help the user identify the target commit, then ask.
2. **Revert**: `git revert <hash>`.
3. **Verify**: `git log --oneline -n 5` to confirm the revert commit was created.
4. **Push**: Ask the user if they want to push the revert to the remote.

## Merge to main
Merge the current branch into main.

1. **Identify branch**: `git branch --show-current` - store the name for later.
2. **Clean check**: `git status -sb` - if uncommitted changes exist, stop and run the **Update** workflow first. Do not auto-stash or discard anything.
3. **Fetch**: `git fetch origin` to sync remote state before merging.
4. **Switch to main**: `git checkout main`. If it doesn't exist locally, create it tracking `origin/main`.
5. **Pull main**: `git pull origin main` - ensure main is current.
6. **Merge**: `git merge --no-ff <branch_name> -m "<descriptive merge message>"`. Using `--no-ff` keeps an explicit merge commit in history, making it easier to trace what was introduced.
   - On conflicts: list conflicting files, stop, and summarize so the user can resolve manually. Do not attempt destructive auto-resolution.
7. **Verify**: `git log --oneline -n 5` - confirm the merge commit is present.
8. **Push main**: `git push origin main`.
9. **Confirm sync**: Verify local and remote main are in sync.
10. **Restore context**: Optionally switch back to the original branch so the user can continue working.

## Status
`git status -sb` → briefly state the working tree state (clean, changes pending, etc.).

## Log
`git log --oneline -n 10` → show recent history without excessive output.

## Branch
`git branch --show-current` → state the branch name plainly.
Files in this package (2)
  • AGENTS.md 1 KB
  • SKILL.md 7 KB

Versions

The database has no other skills named github-use.

Database snapshot: 13.11.2026 · package version 06fde015a13c (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100github-workflow
    GitHub workflow automation — branching, committing, pushing, pull requests, issues, and code review. Use when asked to commit, push, create PRs/branches/issues, or manage git workflow.
  • 100github-workflow
    Enforces the gutt GitHub workflow: commit to feature branches, create PRs, request Copilot review before merge. Use this skill whenever interacting with GitHub repos — creating PRs, pushing code, branching, reviewing, or any git operation against a remote, whether via GitHub MCP…
  • 100github-sync
    Review the session's git changes, summarize them for approval, then commit and push to GitHub. Trigger when the user runs /github-sync or says "sync to github", "commit and push", "push this session", "wrap up and push", "save this session to git". For commit-only (no push) or…
  • 100git-github
    Use for any git or GitHub operation in the team repo — creating the repo from the template, branches, PRs with gh, issues, resolving conflicts, and recovering from mistakes.
  • 100git-workflow-guide
    Guide Git branching strategies, branch naming, and merge operations. Use when: creating branches, merging, pull requests, Git workflow questions. Not for: composing the commit message — use /commit; the safety checks around pushing — use /push. Keywords: branch, merge, PR, pull…
  • 100create-pr
    Create Git branches, commits, pushes, and GitHub pull requests for Next.js. Use when the user asks to create a branch, commit current changes, open a PR or draft PR, publish a pull request, or recover from gh pr create / PR template issues. Covers…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.