Build, Commit and Push

Build npm projects and push grouped Git commits to GitHub.

1|Updated Apr 14, 2025
One-click install
npx skills add https://github.com/coolzeta/coolzeta.github.io --skill build-commit-and-push
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Build, Commit and Push
Source: https://github.com/coolzeta/coolzeta.github.io/tree/main/.opencode/skills/build-commit-push
Command: npx skills add https://github.com/coolzeta/coolzeta.github.io --skill build-commit-and-push

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of building your project, ensuring it's error-free before committing and pushing changes to GitHub, preventing broken builds from being merged.

Core Features & Use Cases

  • Automated Build & Validation: Executes npm run build and checks for any errors.
  • Conditional Committing: Only proceeds to commit and push if the build is successful.
  • Intelligent Commit Grouping: Analyzes changes and creates separate, focused commits for different purposes (features, fixes, docs, etc.).
  • Use Case: After implementing a new feature, you can use this skill to automatically build your project, verify there are no errors, and then commit your feature changes and any related documentation updates in separate, well-described commits.

Quick Start

Use the build commit push skill to build the project and push any successful changes.

Frequently Asked Questions about Build, Commit and Push

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

FAQPage Schema
How do I automate git commit and push only after npm run build succeeds?

To automate git commit and push after a successful build, you can validate project integrity by running `npm run build` first. The process conditionally commits and pushes changes to GitHub only if the build completes without errors, preventing broken code from reaching your repository.

How does intelligent commit grouping work for multiple file changes?

Intelligent commit grouping analyzes code changes using `git status` and `git diff` to categorize updates by purpose, such as features, fixes, or documentation. It then creates distinct, focused Git commits for each category to maintain an organized version control history.

Can I prevent broken npm builds from being pushed to GitHub automatically?

You can prevent broken npm builds from being pushed to GitHub by integrating an automated build check into your workflow. The system runs `npm run build` and halts the commit and push process entirely if any build errors are detected.

What is the best way to separate feature and documentation updates into distinct git commits?

The best way to separate feature and documentation updates into distinct git commits is by analyzing file diffs to determine their purpose. The system groups related changes together and creates multiple focused commits before pushing everything to the remote repository.