agentleFS
rayketcham-labrayketcham-lab/qn-claude-web/.claude/skills/commit-push-pr/SKILL.md

commit-push-pr

Skill2 starsChanged 8 months agoApache-2.0View on GitHub

Commit all changes, push to remote, and open a pull request in one shot. The most common inner-loop workflow.

  • Reads credentials
  • Commits and pushes

23 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use docs-ci, docs-interfaces and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • jh941213Skill

    docs-ci

    문서 CI(링크·OpenAPI lint·breaking 게이트·mermaid 검증)나 문서 드리프트 감지(docs.yaml 신선도 검사)를 설치하거나 돌릴 때 사용. 문서 내용 작성은 docs-architecture·docs-interfaces·docs-manuals.

    Also in 3 projects that use this

  • jh941213Skill

    docs-interfaces

    API·이벤트 인터페이스 문서(OpenAPI·swagger·AsyncAPI 명세, 엔드포인트 레퍼런스, API 구성도·시퀀스, API CHANGELOG)를 만들거나 코드와 맞출 때 사용. 시스템 구성도는 docs-architecture, API 설계 원칙은 api-design-principles.

    Also in 3 projects that use this

  • RachaelQuiselSkill

    client-docs

    Client documentation. Use when a build needs documentation updates or missing project documents need to be identified.

    Also in 3 projects that use this

  • planailabsSkill

    docs-architecture

    Layout, build pipeline, and structural gotchas for this dual-Astro repo. Read before changing structure, routing, or adding content. Operational/dev-server questions → dev-build skill.

    Also in 3 projects that use this

  • diego-tobalinaSkill

    build-fix

    Fix build and compilation errors systematically. Run when build fails.

    Also in 3 projects that use this

  • nilecuiSkill

    async-python-patterns

    Master Python asyncio, concurrent programming, and async/await patterns for high-performance applications. Use when building async APIs, concurrent systems, or I/O-bound applications requiring non-blocking operations.

    Also in 3 projects that use this

  • +4 more from jh941213

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 2 are distinctive, and 6 are very specific to this project.

  • 0

    Common

    Most of the 17 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Assess changes: Run git status and git diff --stat to understand what's being committed

    line 15
  2. Very specific:

    Stage intelligently: Add changed/new files by name (never git add -A).

    line 16
  3. Very specific:

    Craft commit message: Follow conventional commit format (feat:, fix:, refactor:, test:, docs:, ci:, security:).

    line 17
  4. Very specific:

    Open PR: Use gh pr create with:

    line 19
  5. Distinctive:

    NEVER push directly to main/master — create a branch first

    line 26
  6. Very specific:

    NEVER commit files matching: .env*, secrets/, credentials*, *.pem, *.key

    line 27
  7. Very specific:

    If gh CLI is not available, commit and push but skip PR creation and tell the user

    line 28
  8. Very specific:

    If creating a new branch, use: claude/<type>/<short-description>

    line 31

“Common” is measured: kept by at least 6 in 10 of the 17 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Commit → Push → PR

Execute the full commit-push-PR workflow in a single invocation.

Steps

  1. Assess changes: Run git status and git diff --stat to understand what's being committed
  2. Stage intelligently: Add changed/new files by name (never git add -A). Skip .env, secrets, credentials, .pem, .key files.
  3. Craft commit message: Follow conventional commit format (feat:, fix:, refactor:, test:, docs:, ci:, security:). Focus on why not what. End with Co-Authored-By: Claude <noreply@anthropic.com>
  4. Push: Push to the current branch with -u flag if no upstream is set. Create a new branch from current if on main/master.
  5. Open PR: Use gh pr create with:
    • Short title (<70 chars)
    • Body with ## Summary (1-3 bullets), ## Test plan (checklist), and Generated with Claude Code footer
  6. Report: Return the PR URL

Safety Checks

  • NEVER force push
  • NEVER push directly to main/master — create a branch first
  • NEVER commit files matching: .env*, secrets/, credentials*, *.pem, *.key
  • If gh CLI is not available, commit and push but skip PR creation and tell the user

Branch Naming

If creating a new branch, use: claude/<type>/<short-description>

  • Example: claude/feat/add-verification-hook
  • Example: claude/fix/ocsp-response-parsing

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.