done

Commits staged changes and pushes the current git branch to remote.

2|2|Updated Dec 23, 2017
One-click install
npx skills add https://github.com/xriu/dotfiles --skill done-xriu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: done
Source: https://github.com/xriu/dotfiles/tree/main/home/.skills/done
Command: npx skills add https://github.com/xriu/dotfiles --skill done-xriu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It removes the repetitive manual steps of finalizing repository work by inspecting git state, committing pending changes, and pushing the current branch in one guided workflow. ## Core Features & Use Cases - State Inspection: Runs git status and checks the current branch before taking any action. - Safe Commit and Push: Stages and commits relevant changes with an appropriate message, then pushes the current branch to remote. - Guardrails: Never merges or rebases into the default branch, and reports conflicts, untracked files, or large files before risky actions. - Use Case: After finishing a feature branch, say "done" to have your changes committed and pushed while integration into main is left entirely to you. ## Quick Start Tell the assistant "done" or "wrap up" to commit your current changes and push the branch to remote.

Frequently Asked Questions about done

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

FAQPage Schema
How do I commit and push my current git branch in one step?▼

Invoke the done workflow by saying "done" or "wrap up". It runs git status, stages and commits relevant changes with an appropriate message, then pushes the current branch to the remote.

How to finalize feature branch work without merging to main?▼

Use this workflow to commit and push only the current branch. It explicitly never merges or rebases into the default branch, leaving all integration decisions to you.

Does this workflow work with git worktrees?▼

Yes, it detects whether the repository uses worktrees and updates the worktree accordingly. If no worktrees are present, that step is skipped automatically.

What happens if there are untracked or large files before pushing?▼

The workflow reports untracked files that should be committed, large files, and potential conflicts before pushing. It surfaces these issues rather than taking risky actions silently.

When should I not use an automated commit-and-push workflow?▼

Avoid it when you need interactive rebase, history rewriting, or selective staging of sensitive changes. Those scenarios require manual git operations with careful review of each hunk.