skills.rest
etylsarin
etylsarinCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

git-workflow

Enforce feature-branch pull request workflows and prevent direct commits to main.

59|12|Updated Feb 26, 2026
Search Tags:#git#branching#code-review#delivery#pull-request#task-tracking#issue-management
One-click install
npx skills add https://github.com/etylsarin/opencastle --skill git-workflow-etylsarin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/etylsarin/opencastle/tree/main/src/orchestrator/skills/git-workflow
Command: npx skills add https://github.com/etylsarin/opencastle --skill git-workflow-etylsarin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents direct commits to main, enforces traceable feature branches, and reduces lost work or unreviewed changes by defining a standardized commit, push, and pull request workflow and discovered-issues policy.

Core Features & Use Cases

  • Branching conventions: Require branches created from main with the pattern type/ticket-id-short-description (e.g., fix/TAS-21-places-redirect-loop) to keep history organized and linkable to task tracker issues.
  • PR Safety Rules: Enforce opening pull requests for all changes, forbid direct merges to main, and prohibit unsafe operations like force-pushing shared branches.
  • Delivery Outcome Checklist: Provide a required checklist for every task: dedicated branch, atomic commits referencing the issue ID, pushed branch, open PR, and linked task tracker entry.
  • Discovered Issues Policy: Mandate searching known issues, tracking new findings in KNOWN-ISSUES.md or creating task-tracker bugs with evidence and remediation options, and include fallback instructions when tracker tools are unavailable.
  • Task Tracking Guidance: Define placeholder values and procedural steps when the task-management MCP tools are not available so work remains actionable and traceable.

Quick Start

Create a feature branch from main, commit referenced work with the tracker ID, push the branch, and open a pull request for review and task linkage.

Frequently Asked Questions about git-workflow

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

FAQPage Schema
How do I prevent direct commits to main and enforce pull request workflows?▼

You can prevent direct commits to main by enforcing feature-branch pull request workflows that require opening pull requests for all changes, forbid direct merges to main, and prohibit unsafe operations like force-pushing shared branches.

What is the standard naming convention for git feature branches linked to task tracker issues?▼

The standard naming convention for git feature branches is type/ticket-id-short-description, such as fix/TAS-21-places-redirect-loop, which keeps repository history organized and linkable to task tracker issues.

How do I track discovered issues in git when task tracker tools are unavailable?▼

When task tracker tools are unavailable, track discovered issues by searching known issues, documenting new findings with evidence and remediation options in a KNOWN-ISSUES.md file, and using placeholder ticket values to keep work traceable.

What items belong on a delivery checklist for a git feature branch?▼

A git delivery checklist includes a dedicated feature branch, atomic commits referencing the issue ID, a pushed branch, an open pull request, and a linked task tracker entry to ensure complete traceability.

Can I use placeholder ticket values for issue management when my MCP task-management tools are missing?▼

Yes, you can use defined placeholder ticket values and procedural steps for issue management when MCP task-management tools are unavailable, ensuring work remains actionable and traceable despite missing task tracker integrations.

Why should I avoid force-pushing shared git branches during code review?▼

Avoid force-pushing shared git branches because it is an unsafe operation that overwrites team contributions, and PR safety rules prohibit it to maintain review integrity and traceable delivery.

Related Skills

Explore More Software Engineering Skills→
jwbaldwinjwbaldwin

work-on-ticket

Fetch Jira ticket details, create a kebab-case branch, and start task planning.

Community
Advanced
nbramianbramia
20

merge-pr

Validate PR readiness, squash-merge, delete remote branch, and update linked GitHub issues.

Community
Advanced
codekilncodekiln
3

pr-lifecycle

Validate worktrees, branch names, issue links, and commit messages for PRs.

Community
Advanced
RyoMurakami1983RyoMurakami1983
2

git-initial-setup

Automates GitLab project and repository setup for streamlined onboarding and management.

Community
Intermediate