Commit push pr

Skill brycewang-stanford/Auto-Empirical-Research-Skills/skills/09-meleantonio-awesome-econ-ai-stuff/_skills/engineering/commit-push-pr

🔬 A curated collection of 23,000+ agent skills for empirical research across 8 social science disciplines. | 精选 23,000+ AI Agent 技能库，覆盖8大社会科学学科的实证研究。CoPaper.AI 20分钟完成一篇可复现的规范实证论文，并支持用户上传 Skills。-- Maintained by CoPaper.AI from Stanford REAP.

Install

npx -y skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill commit-push-pr

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.

What its author says it does

Copied from the file, not written here

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

SKILL.md

2.0 KB, as published. Nobody here has run it

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

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.)
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)
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"
Push to Remote
- Push the branch: git push -u origin HEAD
- If branch doesn't exist on remote, create it
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.