OpenParable
Skip to content
← Back to skills

Commit Push PR

Development
commit-push-pr

Commit Push PR is an Agent Skill for development published in the brycewang-stanford/Auto-Empirical-Research-Skills repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Commit changes, push to remote, and create a pull request. Use for completing features or fixes ready for review.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/brycewang-stanford/Auto-Empirical-Research-Skills/blob/HEAD/skills/09-meleantonio-awesome-econ-ai-stuff/_skills/engineering/commit-push-pr/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/commit-push-pr, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Commit, Push, and Create PR

Automate the git workflow for completing a feature or fix.

Pre-computed Context

Before proceeding, gather this information:

  • Current branch: !git branch --show-current
  • Git status: !git status --short
  • Recent commits on this branch: !git log --oneline -5
  • Diff summary: !git diff --stat

Workflow

  1. Review Changes

    • Check git status for all modified/added files
    • Review the diff to understand what's being committed
    • Ensure no sensitive files are staged (.env, credentials, etc.)
  2. Run Pre-commit Checks

    • Format code: ruff format . (if Python files changed)
    • Lint code: ruff check . (if Python files changed)
    • Run tests: pytest (if tests exist)
  3. Stage and Commit

    • Stage relevant files: git add <files>
    • Create a commit with Conventional Commits format:
      • feat: for new features
      • fix: for bug fixes
      • docs: for documentation
      • refactor: for refactoring
      • test: for tests
      • chore: for maintenance
    • Write a clear, concise commit message focusing on "why"
  4. Push to Remote

    • Push the branch: git push -u origin HEAD
    • If branch doesn't exist on remote, create it
  5. Create Pull Request

    • Use GitHub CLI: gh pr create
    • Include:
      • Clear title summarizing the change
      • Description with summary and context
      • Reference any related issues
    • Add appropriate labels if applicable

Arguments

Pass a commit message or leave empty for auto-generated message based on changes.

Usage: /commit-push-pr [optional commit message]

Example: /commit-push-pr feat: add user authentication

Output

Return the PR URL when complete.