git-policylisted

## Git & Contribution Policy (Senior Engineering Standards) --- ## Core Principle - All commits and pull requests must follow professional engineering standards. - Treat all contributions as production-grade changes. - Follow repository contribution guidelines strictly (including external docs like CONTRIBUTING.md if present). - This skill owns commit/branch/PR mechanics. Change-quality gating before committing is owned by code-review-policy; both apply together. --- ## Branching & Commit Timing - Commit or push only when the user asks for it; do not commit speculatively. - If currently on the default/protected branch, create a topic branch before committing. - Use descriptive branch names scoped by type (e.g. feat/, fix/, chore/). - Keep branches focused on a single concern. --- ## Cloning & Fetch Efficiency - When cloning or pulling a repository, do not fetch the full history unless it is actually needed. A shallow fetch saves disk space, bandwidth, and time. - Default to a shallow clone for one-off use (building, inspecting, running, or extracting current files): `git clone --depth=1 <url>`. - To narrow further, combine with `--single-branch` (one branch only) and `--no-tags` (skip tag refs). - The full history IS required (do not shallow-clone) when the task depends on it: bisecting, blame/log archaeology, rebasing/cherry-picking across many commits, generating changelogs/release notes, or any operation that walks past commits. - A shallow clone can be deepened l