Copilot-Skills: Instructions file for GitHub Copilot

.github/instructions/git-ops.instructions.md

Copilot-Skills git-ops.instructions.md is an instructions file for GitHub Copilot from TheSethRose/Copilot-Skills. It costs 1,811 tokens per session, scanned A, original, MIT.

Guidance for Git version control tasks such as commits, merges, rebases, branches, and pull requests, which are requests to combine or share code changes.

In plain words
What is it for?
Use it when checking repository state, preparing commits, synchronizing branches, resolving conflicts, or managing GitHub changes.
Why use it?
It adds safety checks around operations that can alter project history or send changes to a shared repository.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file.

This is TheSethRose/Copilot-Skills's own configuration. It tells GitHub Copilot how to work on Copilot-Skills itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Copilot-Skills configures →

Reuse

Borrowing it

Nothing to install: this file belongs to TheSethRose/Copilot-Skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/TheSethRose/Copilot-Skills/main/.github/instructions/git-ops.instructions.md
Clone the repo
git clone --depth 1 https://github.com/TheSethRose/Copilot-Skills

Made for: GitHub Copilot.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for Copilot-Skills git-ops.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/thesethrose/copilot-skills/git-ops/github.svg)](https://agentmods.dev/instructions/thesethrose/copilot-skills/git-ops)
Your own site
<a href="https://agentmods.dev/instructions/thesethrose/copilot-skills/git-ops"><img src="https://agentmods.dev/badge/instructions/thesethrose/copilot-skills/git-ops/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for Copilot-Skills git-ops.instructions.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/thesethrose/copilot-skills/git-ops"><img src="https://agentmods.dev/badge/instructions/thesethrose/copilot-skills/git-ops.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,811 This file is loaded in full into every session.
When invoked 1,811 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.01811 $0.01811
Opus 5.5 $0.00724 $0.00724
Sonnet 5.5 $0.00362 $0.00362
Haiku 4.5 $0.00181 $0.00181

Measured 1mo ago against content hash 5c6a3ee4749b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

Copilot-Skills git-ops.instructions.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.github/instructions/git-ops.instructions.md · 246 lines

How it starts

The opening of the file, as written. The whole thing — 246 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Git Operations - Automatic Context Instructions

Related Prompt: /git-ops
Related Skill: .github/copilot-skills/git-ops/SKILL.md

Triggers: git, commit, merge, rebase, push, pull, branch, checkout, stash, conflict, github, pull request, PR, force push

Context: Git Version Control Operations

When working with Git-related files or when user queries contain version control keywords, this context is automatically activated.

Core Principles

Safety First

  • Always check status before destructive operations
  • Create backups before force operations or history rewrites
  • Verify branch before pushing or merging
  • Preview changes with --dry-run flags when available

Professional Workflow

  • Atomic commits - One logical change per commit
  • Descriptive messages - Use conventional commit format
  • Feature branches - Never commit directly to main/master
  • Pull before push - Always sync with remote first

Default Behaviors

When user mentions "commit"

  1. Suggest /git-ops skill prompt
  2. Run git status to show current state
  3. Use conventional commit format: type(scope): message
  4. Validate commit message length and format
  5. Check for common mistakes (large files, secrets, debug code)

When user mentions "merge" or "rebase"

  1. Suggest /git-ops skill prompt
  2. Check current branch (prevent accidental main branch operations)
  3. Verify working directory is clean
  4. Show merge/rebase preview
  5. Prepare conflict resolution strategy

When user mentions "push" or "force"

  1. Suggest /git-ops skill prompt with safety warnings
  2. Load .github/copilot-skills/git-ops/safety.md for force push guidelines
  3. Verify remote branch state
  4. Use --force-with-lease instead of --force
  5. Confirm push target is correct

When user mentions "conflict"

  1. Suggest /git-ops skill prompt
  2. Show conflict files with git status
  3. Use bundled script: .github/copilot-skills/git-ops/scripts/conflict_resolver.sh
  4. Explain merge markers and resolution strategies

Read the full file on GitHub · 246 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 246 lines · 1,811 tokens per session scan A 5c6a3ee4749b

Subscribe to this mod's changes

Copilot-Skills git-ops.instructions.md is an instructions file published in the GitHub repository TheSethRose/Copilot-Skills (3 stars, last pushed 10mo ago), licensed MIT. It adds 1,811 tokens to every session, about $0.0072 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,715 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,581 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens