skills.rest
FernanSuoza
FernanSuozaCOMMUNITY
Explore all skills by this author →
GitHub

core-story-delivery-and-commit-workflow

Enforce branch, commit, and pull request discipline for backlog items.

Updated Mar 22, 2026
Search Tags:#git#branching#pre-commit#pull-requests#conventional-commits#review-packets#commit-workflow
One-click install
npx skills add https://github.com/FernanSuoza/AIDD-project-bootstrap --skill core-story-delivery-and-commit-workflow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: core-story-delivery-and-commit-workflow
Source: https://github.com/FernanSuoza/AIDD-project-bootstrap/tree/main/templates/skills/core-story-delivery-and-commit-workflow
Command: npx skills add https://github.com/FernanSuoza/AIDD-project-bootstrap --skill core-story-delivery-and-commit-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Projects often produce large, unfocused branches and commits that are hard to review and trace back to backlog items, which slows delivery and reduces auditability. This Skill defines a disciplined, repeatable workflow so each backlog item becomes a small, reviewable, and traceable Git change.

Core Features & Use Cases

  • Enforces one delivery branch per backlog item and clear branch naming for US-, HUS-, and BUG- work items.
  • Installs and configures Git hooks and a commit template to validate Conventional Commits and require work-item IDs.
  • Provides pre-commit checks that block generated or local-only artifacts and detect potential secret files.
  • Defines pull request and review packet expectations, a pause/resume protocol for blocked stories, and guidance for draft PRs and review-ready transitions.
  • Use case: an AI or developer opens a short-lived us/US-123 branch, makes focused commits validated by hooks, attaches a review packet, and opens a draft PR for early feedback.

Quick Start

Install the story workflow to set the commit template and enable the commit-msg and pre-commit hooks so commits require Conventional Commit formatting and work-item IDs.

Frequently Asked Questions about core-story-delivery-and-commit-workflow

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

FAQPage Schema
How do I enforce conventional commits and work-item IDs in my git workflow?▼

To enforce conventional commits and work-item IDs, install a commit-msg hook and configure a commit template that validates commit messages. This ensures each git commit is traceable to a specific backlog item and formatted correctly.

What's the best way to keep git branches small and reviewable for backlog items?▼

Keeping git branches small and reviewable requires enforcing one delivery branch per backlog item with clear naming conventions. This disciplined workflow produces focused, traceable Git changes that simplify the pull request review process.

How do I block generated artifacts and secret files from being committed?▼

Blocking generated artifacts and secret files from commits is handled by pre-commit hooks. These hooks detect potential secret files and block local-only artifacts before they enter the repository history.

Can I use draft pull requests for early feedback on a paused story?▼

Yes, you can use draft pull requests for early feedback. The workflow defines a pause and resume protocol for blocked stories, allowing you to open a draft PR and attach a review packet when transitioning to review-ready.

Does this commit workflow support US, HUS, and BUG backlog items?▼

Yes, this commit workflow fully supports US, HUS, and BUG backlog items. It applies branch and commit discipline across implementation, bug fixing, review, and merge preparation for all these work-item types.

Why do my pull requests lack traceability back to the original backlog item?▼

Pull requests lack traceability when commits are not linked to backlog items. Requiring work-item IDs in commit messages and attaching a review packet ensures every Git change is auditable and traceable back to its source story.

Related Skills

Explore More Software Engineering Skills→
alexandersumeralexandersumer
1

git-publish-to-origin

Commit and push the current Git branch to the origin repository with safety checks.

Community
Intermediate
taloncjonestaloncjones

ship

Automate code review, testing, version bump, merge, and post-merge cleanup for pull requests.

Community
Advanced
YoshikemoloYoshikemolo
5

git-jira-integration

Generate Git branch names and validate commit messages against Jira issues.

Community
Intermediate
hw-native-syshw-native-sys
101

git-commit

Automate Git commits with pre-commit hooks, testing, and linting.

Official
Advanced