git-workflow-and-versioning

Structures git commits, branching, and pre-commit verification for code changes.

Updated May 27, 2026
One-click install
npx skills add https://github.com/Rkaaaa404/cyberhack-SYDT --skill git-workflow-and-versioning-rkaaaa404
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-workflow-and-versioning
Source: https://github.com/Rkaaaa404/cyberhack-SYDT/tree/main/.agents/skills/git-workflow-and-versioning
Command: npx skills add https://github.com/Rkaaaa404/cyberhack-SYDT --skill git-workflow-and-versioning-rkaaaa404

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI agents and developers generating code at high speed often produce giant unreviewable commits, vague messages, and tangled branches. This Skill enforces disciplined version control so every change stays reviewable, reversible, and deployable. ## Core Features & Use Cases - Atomic Commit Discipline: Enforces small, single-purpose commits with conventional message types (feat, fix, refactor, test, docs, chore) and a save-point pattern for reverting failed changes. - Trunk-Based Branching Strategy: Keeps main always deployable with short-lived feature/fix branches, standard naming conventions, and AWS Amplify deployment awareness. - Pre-Commit Hygiene Checklist: Provides verification steps covering staged diffs, secret scanning, tests, linting, type checking, and builds before every commit. - Use Case: After an AI agent implements a new API endpoint, use this Skill to split the work into atomic commits, write descriptive messages, scan for leaked secrets, and merge through a clean short-lived branch. ## Quick Start Use the git workflow skill to review my current uncommitted changes and organize them into atomic commits with proper messages.

Frequently Asked Questions about git-workflow-and-versioning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write good git commit messages?▼

Use the format type: short description, where type is one of feat, fix, refactor, test, docs, or chore. Add an optional body explaining why the change was made rather than what changed, since the diff already shows the what.

What is trunk-based development with git?▼

Trunk-based development keeps main always deployable while work happens in short-lived feature branches merged back within 1-3 days. Pushes to main can trigger deployment pipelines such as AWS Amplify builds.

How large should a git commit be?▼

Around 100 lines is easy to review and revert, 300 lines is acceptable for a single logical change, and 1000 lines should be split into smaller commits. Each commit should do exactly one logical thing.

How do I prevent committing secrets to git?▼

Run git diff --staged and grep for patterns like password, secret, api_key, and token before committing. Also set up a .gitignore immediately so .env files, node_modules, and build artifacts are never staged.

When should I use feature flags instead of long-lived branches?▼

Prefer feature flags whenever work cannot merge within 1-3 days, since long-lived branches diverge from main and create painful merges. Short-lived branches keep integration continuous and history clean.