skills.rest
Eyhenij
EyhenijCOMMUNITY
Explore all skills by this author →
GitHub

git-workflow

Enforces GitHub delivery workflow rules for tasks, branches, commits, PRs, and merges.

1|Updated Jan 14, 2024
Search Tags:#git#code review#pull request#github#branch naming#project board#commit convention
One-click install
npx skills add https://github.com/Eyhenij/rt-tools --skill git-workflow-eyhenij
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/Eyhenij/rt-tools/tree/main/.claude/skills/git-workflow
Command: npx skills add https://github.com/Eyhenij/rt-tools --skill git-workflow-eyhenij

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Teams working in a GitHub-hosted repository need consistent discipline around task tracking, branch naming, commit formats, PR creation, and merge order. This Skill encodes the full delivery workflow as enforceable rules so an AI agent creates tasks, branches, commits, and pull requests exactly the way the repository requires, with guards catching violations before they reach the remote. ## Core Features & Use Cases - Task and branch pairing: Creates a GitHub issue and board card, then derives the branch name in the form RT-<number>-<slug> so every PR traces back to a tracked task. - Delivery guards: Refuses commits to the main branch, PRs from branches without task numbers, force pushes on stacked branches, and destructive commands like reset --hard on dirty trees. - Board and PR automation: Ships scripts/board.sh to add issues to the GitHub Projects board and move their Status column, plus reference forms for PR bodies and changelog entries. - Use Case: An agent picks up task RT-88, creates the branch RT-88-add-select-button from the epic branch, commits with a conventional-commit subject, pushes as the machine account, and opens a draft PR whose body links the task with Closes #88. ## Quick Start Ask the agent to create a task and branch for a new piece of work, then commit, push, and open a pull request following this repository's delivery rules.

Frequently Asked Questions about git-workflow

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

FAQPage Schema
How do I enforce branch naming conventions in a GitHub workflow?▼

Branch names follow the form RT-<task number>-<short-slug>, derived from the task key configured in the repository's checks settings. A delivery guard hook parses branch-creation commands and refuses names that do not match the required pattern.

How do I link GitHub pull requests to project board tasks automatically?▼

Add a Closes #<number> line to the PR body so the task closes on merge, and move the board column explicitly with the task:move command. The board card and PR stay linked through the issue number referenced in both.

Can I commit directly to the main branch with this workflow?▼

No. A guard hook inspects every commit command, reads the current branch, and refuses any commit targeting main. All changes must go through a task branch and a reviewed pull request.

Why does a force push close a stacked pull request as merged?▼

GitHub marks a PR merged once its branch tip becomes reachable from the base branch. Rewriting the lower branch of a stack with rebase or force push triggers this, so the rules prohibit history rewrites on lower branches and fix lag by merging main in.

What commit message format does this workflow require?▼

Commits use the conventional format type(scope): description with types like feat, fix, refactor, docs, and chore, validated by commitlint through a git hook. In this repository the description must also be written in Russian.

When should a pull request be opened as a draft?▼

Open a draft with gh pr create --draft whenever the work still waits on a pipeline run, rework, or an answer. If the pipeline never runs for that base branch, open the PR ready instead, since a draft would block the merge button for no reason.

Related Skills

Explore More Software Engineering Skills→
sarkarshivaditya-labsarkarshivaditya-lab

issue-prerequisite

Enforces a hard gate requiring a verified GitHub issue before any work begins.

Community
Intermediate
AzureAzure
27

hotfix-release

Publish npm package hotfixes from Azure TypeSpec release branches with validation and backmerges.

Official
Advanced
mojwangmojwang

neon-branch-cleanup

Delete stale Neon database branches while preserving primary branches and open PRs.

Community
Advanced
novel-jpnovel-jp

learn-gw-branch

Teach task-linked branch naming for trunk-based Git workflows.

Official
Intermediate