save-work

Commit, push to multiple remotes, and merge Git branches.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/RagnarokButMemorySafe/opencode-config --skill save-work
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: save-work
Source: https://github.com/RagnarokButMemorySafe/opencode-config/tree/main/skills/save-work
Command: npx skills add https://github.com/RagnarokButMemorySafe/opencode-config --skill save-work

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that your completed work is safely stored, versioned, and integrated into the main codebase, preventing data loss and maintaining a clean project history.

Core Features & Use Cases

  • Automated Committing: Groups changes into logical commits using conventional commit standards.
  • Multi-Remote Pushing: Pushes commits to all required Git remotes, including canonical and secondary publish remotes.
  • PR Creation & Merging: Creates or updates Pull Requests for feature branches and merges them into the base branch.
  • Worktree Hygiene: Cleans up old or integrated worktrees to maintain a tidy local environment.
  • Use Case: After finishing a feature, you can run this Skill to automatically commit your changes, push them to GitHub and your internal GitLab, create a PR, and merge it, all with a single command.

Quick Start

Run the save-work skill to commit, push, and merge your current changes.

Frequently Asked Questions about save-work

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

FAQPage Schema
How do I automate committing and pushing code to multiple Git remotes?

Automating Git commit and push operations groups changes into logical conventional commits and pushes them to all configured remotes, including canonical and secondary publish targets. This prevents data loss by ensuring your completed work is safely stored across multiple repositories.

What is the best way to merge a feature branch and create a pull request automatically?

Merging a feature branch automatically analyzes your Git repository state, plans commits, creates or updates Pull Requests for your feature branches, and merges them into the base branch. This ensures your work is integrated into the main codebase while maintaining a clean project history.

Can I use a single command to commit, push to GitHub, and merge my current changes?

You can use a single command to commit, push to GitHub and internal remotes like GitLab, create a PR, and merge your changes. The process handles the entire workflow from worktree state analysis to PR creation and merging automatically.

How does worktree hygiene work when integrating feature branches?

Worktree hygiene cleans up old or integrated worktrees to maintain a tidy local environment after merging. This prevents local repository clutter and ensures your development workspace remains organized after your code is integrated into the main branch.

Why should I use conventional commit standards for grouping code changes?

Using conventional commit standards for grouping code changes ensures logical commits and maintains a clean project history. This approach automates commit planning based on your Git repository state analysis, providing detailed summaries of actions taken.