git-pushing

Automate staging, committing, and pushing changes for the Blured Engine repository and submodules.

15|1|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/bluredengine/blured --skill git-pushing-bluredengine
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-pushing
Source: https://github.com/bluredengine/blured/tree/main/.claude/skills/git-pushing
Command: npx skills add https://github.com/bluredengine/blured --skill git-pushing-bluredengine

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill simplifies the git workflow by automating the staging, committing, and pushing of changes to your Blured Engine repository and its submodules.

Core Features & Use Cases

  • Automated Git Workflow: Handles the entire git workflow, from staging to pushing changes.
  • Submodule Management: Manages changes in submodules like godot and opencode.
  • Custom Commit Messages: Allows for custom commit messages to be applied to all repositories with changes.
  • Use Case: When you want to commit and push changes to your Blured Engine project, this Skill automates the process, ensuring that all changes are committed and pushed correctly.

Quick Start

Run the script to stage, commit, and push changes to your Blured Engine repository: bash "<workspace>/.claude/skills/git-pushing/scripts/smart_commit.sh" "feat: add feature"

Frequently Asked Questions about git-pushing

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

FAQPage Schema
How do I automate git staging, committing, and pushing changes for a repository with submodules?

Automating git staging, committing, and pushing for a repository with submodules requires a script that handles nested changes and applies conventional commit messages across all active modules. This Skill automates that exact workflow for the Blured Engine.

What is the best way to commit and push git submodules like godot and opencode?

Committing and pushing git submodules like godot and opencode is managed by this Skill, which detects changes within nested repositories and applies your custom commit message to all submodules before pushing them to the remote.

Can I use a single custom commit message for both the main repository and its submodules?

Yes, you can use a single custom commit message for both the main repository and its submodules. The Skill takes one conventional commit message as input and applies it to all repositories that contain changes.

Does this git workflow automation require any external dependencies?

This git workflow automation does not require any external dependencies. It runs as a standalone shell script within your workspace and only requires a standard git installation to function.

How do I run the script to stage, commit, and push changes with a conventional commit message?

To stage, commit, and push changes, run the shell script located in the workspace .claude/skills directory and pass your conventional commit message as an argument to execute the automated git workflow.

Why use this script instead of manually running git commands for each submodule?

Using this script instead of manual git commands ensures consistent conventional commit practices across the main repository and all submodules. It eliminates the risk of missing nested changes and prevents desynchronized commit histories.