Skip to content
All Skills

Commit

Stage, commit, and push changes to the current branch. Use when asked to commit, push, or create a commit for the current task.

Software Engineering|v1|Updated 7/14/2026|GitHub source
MCP get_skill({ skillId: "commit-3b85cc0a" })

Use this skill with your agent

Create a free account and connect via MCP

Get Started Free
# Commit and Push Skill

1. Stage only files related to the current task
2. Run `git commit --no-verify` if pre-commit hooks fail on unrelated issues
3. Push to the current branch
4. Report the commit hash and branch name

NOTE: This repo uses Azure DevOps. For PRs use `az repos pr create`.
NOTE: The `commit-msg` hook strips `Co-Authored-By` trailers so commits appear as sole-author.

---

## Gotchas

- **`git commit --no-verify` bypasses pre-commit hook** — logged in reflog but easy to forget. A CI check that fails on no-verify trailers prevents drift.
- **`commit-msg` hook transforms the message AFTER the editor closes** — verify the final state with `git show -s --format=%B`, not the editor draft.
- **Azure DevOps strips `Co-Authored-By` server-side** — local commits show co-author; PR display doesn't. Test what shows in the PR UI before assuming attribution worked.
- **`git commit` on a detached HEAD creates an orphan** — `git checkout main` loses it unless you branch first. Reflog recovers but only for 30 days.
- **Trailing whitespace in commit messages**: some hooks normalize, some preserve. Format-checks comparing raw vs normalized fail confusingly.
#broad-capability#devops#azure#kubernetes#productivity#version#controlgit

Related Skills

More skills in Software Engineering

Accessibility Standards

Comprehensive web accessibility standards based on WCAG 2.2 AA, with 38+ anti-patterns, legal enforcement context (EAA, ADA Title II), WAI-ARIA patterns, and framework-specific fixes for modern web frameworks and libraries.

#github-copilot#accessibilityMIT

Accord

Authoring unified specification packages across Business/Development/Design teams via staged elaboration (L0 Vision → L1 Requirements → L2 Team Detail → L3 Acceptance Criteria). No code. Use when authoring cross-team specs, building L0-L3 packages, or aligning Biz/Dev/Design on a single source of truth.

#broad-capability#developmentMIT

Acquire Codebase Knowledge

Use this skill when the user explicitly asks to map, document, or onboard into an existing codebase. Trigger for prompts like "map this codebase", "document this architecture", "onboard me to this repo", or "create codebase docs". Do not trigger for routine feature implementation, bug fixes, or narrow code edits unless the user asks for repository-level discovery.

#github-copilot#documentationMIT

Acreadiness Assess

Run the AgentRC readiness assessment on the current repository and produce a static HTML dashboard at reports/index.html. Wraps `npx github:microsoft/agentrc readiness` and hands off rendering to the @ai-readiness-reporter custom agent. Supports policies (--policy) for org-specific scoring. Use when asked to assess, audit, or score the AI readiness of a repo.

#github-copilot#planningMIT

Acreadiness Generate Instructions

Generate tailored AI agent instruction files via AgentRC instructions command. Produces .github/copilot-instructions.md (default, recommended for Copilot in VS Code) plus optional per-area .instructions.md files with applyTo globs for monorepos. Use after running /acreadiness-assess to close gaps in the AI Tooling pillar.

#github-copilot#skillMIT

Acreadiness Policy

Help the user pick, write, or apply an AgentRC policy. Policies customise readiness scoring by disabling irrelevant checks, overriding impact/level, setting pass-rate thresholds, or chaining org baselines with team overrides. Use when the user asks about strict mode, AI-only scoring, custom weights, CI gating, or wants org-wide standardisation.

#github-copilot#planningMIT