rebuild-commit-restart

Name: rebuild-commit-restart
Availability: InStock
Author: ridopark

Rebuild the backend, commit staged changes, and restart services via tmux.

1|Updated Mar 4, 2026

Search Tags:#git #ci/cd #commit #docker #restart #deploy #rebuild

Ready to run

npx skills add https://github.com/ridopark/oh-my-opentrade --skill rebuild-commit-restart

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: rebuild-commit-restart
Source: https://github.com/ridopark/oh-my-opentrade/tree/main/.claude/skills/rebuild-commit-restart
Command: npx skills add https://github.com/ridopark/oh-my-opentrade --skill rebuild-commit-restart

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of deploying local code changes by automating the backend rebuild, code commit, and service restart, ensuring a smooth transition from development to a running state.

Core Features & Use Cases

Full Deployment Cycle: Executes a complete rebuild, commit, shutdown, and restart sequence.
Version Control Integration: Leverages a git-commit-helper skill for standardized commit messages.
Service Management: Gracefully shuts down and restarts core services (omo-core, omo-dashboard) using tmux.
Use Case: After making several updates to the backend trading logic, you want to commit these changes and ensure the entire application is running with the latest code.

Quick Start

Execute the rebuild, commit, and restart process for the application.

Frequently Asked Questions about rebuild-commit-restart

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

FAQPage Schema

How do I automate backend rebuild and service restart for local code changes?▼

Automating backend rebuild and service restart requires a script that rebuilds the backend, commits staged changes, shuts down existing services, and restarts all application components to ensure a repeatable deployment workflow.

What is the best way to deploy local changes and ensure services are running the latest code?▼

Deploying local changes confidently requires a full deployment cycle: rebuilding the backend, committing code, gracefully shutting down existing services, and restarting components. This approach ensures the entire application runs the latest code.

Does this deployment workflow handle shutting down and restarting services managed in tmux?▼

Yes, this deployment workflow gracefully shuts down and restarts core services like omo-core and omo-dashboard managed in tmux. It verifies service status post-restart to ensure all application components are running correctly.

Can I integrate standardized git commit messages into my automated rebuild and restart process?▼

You can integrate standardized git commit messages into the rebuild and restart process. The workflow leverages a git-commit-helper skill to commit staged changes before shutting down and restarting services.

When do I need to use a full deployment cycle script instead of manually restarting services?▼

A full deployment cycle script is needed when you want a repeatable and reliable deployment workflow for local code changes. It ensures code integrity through staged commits and verifies service status post-restart, unlike manual restarts.