smart-recipe-planner-git

Automate Git workflow standards, conventional commits, and PR management.

2|Updated Oct 14, 2025
One-click install
npx skills add https://github.com/LuisDavidTF/Culina-Smart --skill smart-recipe-planner-git
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smart-recipe-planner-git
Source: https://github.com/LuisDavidTF/Culina-Smart/tree/main/.agent/skills/smart-recipe-planner-git
Command: npx skills add https://github.com/LuisDavidTF/Culina-Smart --skill smart-recipe-planner-git

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates Git workflow standards, conventional commits, and PR management.

Core Features & Use Cases

  • Standardized commits with conventional-commit messages to speed up reviews and changelogs.
  • Automated PR descriptions, templates, and review guidelines to improve consistency across repositories.
  • Branch naming and PR flow enforcement across multiple projects to reduce integration friction.

Quick Start

Use this skill to configure and manage GitHub PR processes. Ensure gh CLI is installed and authenticated, then invoke the guidance to create PRs, fill templates, and enforce commit conventions.

Frequently Asked Questions about smart-recipe-planner-git

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

FAQPage Schema
How do I automate conventional commits and PR management across multiple repositories?

You can automate conventional commits and PR management by applying standardized branch naming, commit types, and PR templates. This enforces workflow standards and reduces integration friction across multiple repositories using CLI-based pre-push checks.

How do I enforce branch naming conventions before pushing code?

Branch naming conventions are enforced through pre-push checks and CLI validation. This ensures developers follow prescribed branch strategies across projects before code integration, reducing friction and maintaining repository consistency.

Can I use gh CLI to standardize PR descriptions and templates?

Yes, you can use an authenticated gh CLI to standardize PR descriptions and templates. This automates the PR flow, applies review guidelines, and improves consistency across repositories.

What is the best way to standardize commit messages for faster code reviews?

Standardizing commit messages with conventional-commits formats speeds up reviews and changelogs. This approach applies prescribed commit types and frontmatter metadata to streamline the review process.

Does this Git workflow automation require specific CI validation tools?

Git workflow automation requires an installed and authenticated gh CLI to manage PR processes. It integrates with CI validation to enforce commit conventions and branch strategies across multiple repositories.

Why do I need frontmatter metadata in my pull requests?

Frontmatter metadata satisfies specific repository requirements for PR flow and commit conventions. It ensures prescribed commit types and branch naming conventions are met before CI validation runs.