Instruction file imported from jasonstcyrx/ai-template (.github/instructions/branch-review-process.instructions.md). Copyright stays with the author.

Branch Review Process

Name: branch-review-process
Author: jasonstcyrx

Overview

All code changes must go through a thorough review process before being merged into the main branch. This ensures code quality, consistency, and knowledge sharing across the team.

Review Requirements

Mandatory Review

All pull requests require at least one approval from a qualified reviewer
No self-approvals are permitted
Direct pushes to main branch are strictly prohibited

Reviewer Qualifications

Must be a team member with appropriate permissions
Should have knowledge of the codebase and technologies used
Must not be the author of the pull request

Review Process

1. Pull Request Creation

Create a pull request with a clear, descriptive title
Provide a detailed description of changes
Include any relevant issue numbers or context
Add appropriate labels and assignees

2. Code Review Checklist

Reviewers must verify:

Code follows project coding standards
No obvious bugs or logical errors
Appropriate error handling is implemented
Tests are included and passing
Documentation is updated if needed
No security vulnerabilities introduced
Performance implications considered

3. Review Timeline

Standard reviews: Respond within 24 hours
Urgent fixes: Respond within 4 hours (use appropriate labels)
Large changes: May require multiple reviewers

4. Approval Process

LGTM (Looks Good To Me) approval required
Address all review comments before merging
Resolve any merge conflicts
Ensure CI/CD pipeline passes

Merge Guidelines

Merge Strategy

Use squash and merge for feature branches
Use rebase and merge for hotfixes
Maintain clean commit history

Post-Merge

Delete feature branches after successful merge
Update any related documentation
Notify stakeholders of significant changes

Escalation

If a review is blocked or requires additional input:

Tag appropriate team leads
Schedule a code review meeting if needed
Document decisions and rationale

Compliance

All team members must follow this process
Exceptions require approval from team lead
Regular audits ensure process adherence

{ "ocm": "1", "id": "jasonstcyrx-ai-template-branch-review-process-instructions", "kind": "skill", "name": "branch-review-process", "description": "Branch Review Process", "publisher": "jasonstcyrx", "version": "1.0.0", "capabilities": { "domains": [ "general" ], "tags": [ "skill-md", "github-instructions" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Branch Review Process" ], "primary": false, "metadata": { "source": { "provider": "github-instructions", "repository": "https://github.com/jasonstcyrx/ai-template", "path": ".github/instructions/branch-review-process.instructions.md", "ref": "7b4792467801b41f87a13e49d1dd63a9fa487a4d", "url": "https://github.com/jasonstcyrx/ai-template/blob/7b4792467801b41f87a13e49d1dd63a9fa487a4d/.github/instructions/branch-review-process.instructions.md", "key": "jasonstcyrx/ai-template/.github/instructions/branch-review-process.instructions.md" }, "applies_to": "**" }, "instructions": "# Branch Review Process\n\n## Overview\nAll code changes must go through a thorough review process before being merged into the main branch. This ensures code quality, consistency, and knowledge sharing across the team.\n\n## Review Requirements\n\n### Mandatory Review\n- **All pull requests** require at least one approval from a qualified reviewer\n- **No self-approvals** are permitted\n- **Direct pushes to main branch** are strictly prohibited\n\n### Reviewer Qualifications\n- Must be a team member with appropriate permissions\n- Should have knowledge of the codebase and technologies used\n- Must not be th", "cost": { "context_tokens": 553 } }

branch-review-process

About