git-workflow

Automate Git workflows for Laravel and JavaScript projects with conventional commits.

20|5|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/nasrulhazim/agent-skills --skill git-workflow-nasrulhazim
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/nasrulhazim/agent-skills/tree/main/skills/git-workflow
Command: npx skills add https://github.com/nasrulhazim/agent-skills --skill git-workflow-nasrulhazim

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Git repositories often suffer from inconsistent workflows, misaligned commits, and manual release processes that slow teams down. This Skill automates and standardizes Git workflows for Laravel and JavaScript projects, aligning commits, changelogs, releases, branches, and templates.

Core Features & Use Cases

  • Conventional commits enforcement, semantic versioning, and automated changelog generation.
  • Branch strategy scaffolding, pre-commit hooks, and PR template generation for consistent workflows.
  • Templates and .gitignore scaffolding to maintain repository hygiene across PHP and Node ecosystems.

Quick Start

Put a new project under version control and run the framework-ready setup to enforce conventional commits, create release automation, and apply standard templates.

Frequently Asked Questions about git-workflow

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

FAQPage Schema
How do I automate conventional commits and changelog generation for Laravel and JavaScript projects?

Automate conventional commits and changelog generation by applying standardized Git workflow templates, enforcing semantic versioning, and using deterministic command references for consistent project hygiene across PHP and Node ecosystems.

Can I scaffold branch strategies and pre-commit hooks for multi-repo teams?

Yes, you can scaffold branch strategies and pre-commit hooks for multi-repo teams. The workflow enforces branch protection rules and generates standardized PR templates to maintain repository consistency across projects.

What is the best way to standardize Git workflows from commit messages to releases?

The best way to standardize Git workflows is by enforcing conventional commit formats, scaffolding release automation, and applying standard templates and .gitignore files to align commits, changelogs, and branches.

Does this Git workflow automation support both PHP and Node ecosystems?

Yes, this Git workflow automation explicitly supports both PHP and Node ecosystems. It provides framework-ready setups for Laravel and JavaScript projects to enforce semantic versioning and repository hygiene across multi-repo teams.

How do I set up version control and release automation for a new project?

Put a new project under version control and run the framework-ready setup to enforce conventional commits, create release automation, and apply standard templates for immediate Git workflow standardization.

Why do I need semantic versioning and branch protection rules for my Git repositories?

Semantic versioning and branch protection rules prevent inconsistent workflows and manual release errors. Enforcing these rules aligns commits and changelogs, ensuring stable, standardized releases across multi-repo teams.