commit-push-watch

Stage changes, create conventional commits, push to origin, and monitor CI until terminal results.

7|Updated Dec 5, 2023
One-click install
npx skills add https://github.com/mParticle/aquarium --skill commit-push-watch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-push-watch
Source: https://github.com/mParticle/aquarium/tree/main/.claude/skills/commit-push-watch
Command: npx skills add https://github.com/mParticle/aquarium --skill commit-push-watch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stages changes, creates a conventional commit, pushes to origin, and continuously monitors CI to confirm a successful rollout, reducing manual steps and feedback loops.

Core Features & Use Cases

  • End-to-end git workflow: automatically stage changed files, apply conventional commits, push to the remote, and trigger CI.
  • CI monitoring: watch GitHub Actions (or CI) status until a terminal state is reached, surfacing results and preventing stalled branches.
  • Use Case: When you finish a tweak on a feature branch, run this to ensure the change is committed, pushed, and validated by CI in a single operation.

Quick Start

Run commit-push-watch to stage changes, commit with a conventional message, push to origin, and monitor CI until it passes.

Frequently Asked Questions about commit-push-watch

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

FAQPage Schema
How do I automate git commit, push, and CI monitoring in one step?

You can automate an end-to-end git workflow by using a tool that stages changes, creates a conventional commit, pushes to origin, and streams CI feedback until a terminal result is reached.

How do I enforce conventional commits when pushing to a remote branch?

To enforce conventional commits when pushing to a remote branch, the automation applies conventional-commit formatting during the staging process, ensuring your commit messages meet the required structure before pushing to origin.

Can I push directly to main or master with automated CI monitoring?

No, automated CI monitoring with this workflow avoids pushing directly to main or master. It is designed for feature work and bug fixes across branches, enforcing guardrails to protect your primary branches.

What is the best way to watch GitHub Actions status after pushing code?

The best way to watch GitHub Actions status after pushing code is to use an automated workflow that streams CI feedback continuously until a terminal state is reached, surfacing results and preventing stalled branches.

Does automated CI monitoring have a time limit for watching workflow status?

Yes, automated CI monitoring limits the watch cycle to a defined window with clear guardrails. This prevents stalled branches by ensuring the monitoring session reaches a terminal result within a specific timeframe.