Git Helper

Git workflow automation for commits, pushes, rebases, status checks, and branch operations. Use when working with git repositories for: (1) Checking status,...

Security Scan

The skill's instructions, files, and requirements are coherent with a Git workflow helper: it contains only git guidance, requests no credentials, has no install, and does not attempt unrelated access.

Purpose & Capability

The name/description match the content: SKILL.md and the reference contain only git commands, commit conventions, workflows, and conflict-resolution guidance. There are no unrelated required binaries, environment variables, or external services.

Instruction Scope

Runtime instructions are limited to git operations (status, add, commit, push, pull, rebase, diff, etc.) and referencing the included workflows.md. The guidance explicitly includes safety rules (confirm destructive actions, stay within workspace boundaries). There are no directives to read unrelated files, exfiltrate data, or contact external endpoints.

Install Mechanism

No install spec and no code files — instruction-only. Nothing is written to disk and there are no download or third-party package installation steps.

Credentials

No environment variables, credentials, or config paths are requested. The operations described are standard git commands that do not require extra secrets beyond whatever the user's git/remote setup already uses.

Persistence & Privilege

always is false and the skill does not request persistent or cross-skill configuration. The skill can be invoked autonomously by the agent (platform default), but it does not ask for elevated privileges or to modify other skills.

Assessment

This is an instruction-only Git workflow helper and appears internally consistent. It will direct the agent to run git commands in the user's repository (including potentially destructive commands like rebase, reset --hard, and force-push when explicitly allowed). Before using: (1) ensure the agent is allowed to operate in the target repo and will confirm destructive actions, (2) keep backups or create a safety branch for important work, and (3) avoid granting autonomous invocation over critical repositories unless you trust the agent's permissions and prompts. The lack of code or external installs reduces risk, but remember that any agent using this skill can modify your git history if you authorize it.

Handles all git operations through safe, consistent workflows.

Core Workflows

Status Check

Before any git operation, run git status to understand repository state.

Staging

• git add <file> - Stage specific files
• git add -A - Stage all changes
• git add -p - Interactive staging (review hunks)

Committing

Use Conventional Commits format:

<type>(<scope>): <description>

[optional body]

[optional footer]

Types: feat, fix, docs, style, refactor, test, chore

Scope: Optional, usually the component or area affected

Description: Imperative present tense ("add feature" not "added feature")

Push/Pull

• git push - Push to remote (default: current branch)
• git pull --rebase - Fetch and rebase (preferred default)
• git pull - Fetch and merge (when merge history needed)

Rebasing

• git rebase -i HEAD~N - Interactive rebase last N commits
• Always confirm branch state before rebasing
• Never rebase shared/public branches without explicit permission

Log/Diff

• git log --oneline -N - View last N commits
• git diff - Unstaged changes
• git diff --staged - Staged changes
• git diff HEAD~N - Changes over last N commits

Safety Rules

1. Never force push without explicit user permission
2. Always check status before any operation
3. Confirm destructive actions (rebase, reset, hard, force push)
4. Stay within workspace boundaries - respect user's file access rules
5. Pull before push when working with shared branches

When to Read references/workflows.md

Load this reference file when:

• User needs detailed Conventional Commits specification
• Complex rebase/merge scenarios require guidance
• Branch strategy consultation needed
• Conflict resolution guidance required