done

Commit changes, rebase on main, and create a pull request.

1|1|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/renato0307/rocha --skill done-renato0307
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: done
Source: https://github.com/renato0307/rocha/tree/main/.claude/skills/done
Command: npx skills add https://github.com/renato0307/rocha --skill done-renato0307

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides users to finish a development task by committing changes, rebasing on main, and creating a pull request. It enforces auditable, human-authored history and protects against direct commits to main.

Core Features & Use Cases

  • End-to-end git workflow from local commits to PR creation, including rebases and conflict resolution.
  • Enforces conventional commit messages and review-ready history for multi-commit branches.
  • Handles error conditions with clear guidance to safely complete the workflow.

Quick Start

Run the /done command in a Git-enabled project to start the task completion flow, including pre-flight checks, commits, rebases, and PR creation.

Frequently Asked Questions about done

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

FAQPage Schema
How do I automate a git workflow to commit, rebase, and create a pull request?▼

Automating a git workflow to commit, rebase, and create a pull request is handled by guiding you through pre-flight checks, conventional commits, rebases on main, and PR creation using git and the GitHub CLI. This enforces review-ready, human-authored history.

What is the best way to enforce conventional commits before opening a pull request?▼

Enforcing conventional commits before opening a pull request is achieved by running a guided task completion flow that validates commit messages and prevents direct commits to main. This ensures an auditable and review-ready branch history.

How do I handle git rebase conflicts when finishing a development task?▼

Handling git rebase conflicts when finishing a development task involves built-in safety checks and clear error guidance during the rebase on main. This helps you safely resolve conflicts and maintain a clean, linear commit history.

Do I need the GitHub CLI to automate pull request creation from local commits?▼

Yes, you need the GitHub CLI to automate pull request creation from local commits. The workflow requires standard developer tools like git and the GitHub CLI to execute the end-to-end process and generate the pull request.

Can I prevent direct commits to main while streamlining my git workflow?▼

Preventing direct commits to main while streamlining your git workflow is a core safety feature. The guided flow protects your main branch by enforcing human-authored history and routing changes through a structured pull request.

Why should I rebase on main before creating a pull request?▼

Rebasing on main before creating a pull request ensures your branch has an review-ready, linear history without merge commits. This workflow integrates the latest main branch changes and resolves conflicts locally before PR generation.