managing-git-workflow

The Managing Git Workflow skill provides a comprehensive framework for maintaining code quality and project traceability within the HASH monorepo. It is designed for software engineers and developers contributing to the HASH repository who need to ensure their contributions align with organizational standards. By automating and guiding the interaction between local development and version control, this skill minimizes friction during the transition from local task execution to project integration.

• Standardizes branch naming conventions using the <shortname>/h-XXXX-description pattern, which mandates linking every change to a specific Linear ticket.

• Enforces structured Pull Request (PR) titles (H-XXXX: Description) to ensure clear traceability and easier tracking of development progress.

• Guides users through the implementation of official PR templates, covering critical sections such as purpose, related links, implementation details, and mandatory pre-merge checklists.

• Provides a step-by-step PR review protocol, including command-line tools for fetching full diffs, reviewing inline comments, and verifying Linear issue requirements.

• Facilitates integration with the Linear project management tool by surfacing relevant ticket information for context-aware code reviews.

• Use this skill during every stage of the development lifecycle: when initializing a feature branch, drafting commits, opening a PR, or performing peer code reviews.

• Inputs typically include your developer ID, the target Linear ticket number, and the descriptive intent of the change. Outputs are formatted strings for branches/PRs or checklists for self-verification.

• Ensure all PRs are referenced by their associated H-XXXX ticket number to maintain repository hygiene and history.

• When reviewing code, utilize the provided shell commands (e.g., gh pr diff, gh pr view) to ensure comprehensive visibility of changes rather than truncated summaries.

• Always consult the Pre-merge checklist (covering library changes, documentation, and system impacts) before finalizing any merge requests to maintain high-trust, safety-assured development standards.