agentleFS
renatorozasrenatorozas/claude-code-config/.claude/skills/commit-push-pr/SKILL.md

commit-push-pr

Skill1 starsChanged 8 months agoMITView on GitHub

Commit, push, and open a PR

  • Commits and pushes

We split this skill into the rules it gives an agent

6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 16 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Follow these steps in order:

    line 8
  2. Distinctive:

    Run git status to see what files have changed

    line 10
  3. Distinctive:

    Run git diff to review the changes

    line 11
  4. Distinctive:

    Create a commit with a clear, descriptive message following conventional commits format

    line 13
  5. Very specific:

    Create a Pull Request using gh pr create with:

    line 15
  6. Distinctive:

    If there are any issues at any step, stop and report them.

    line 22

“Common” is measured: kept by at least 6 in 10 of the 16 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

Follow these steps in order:

  1. Run git status to see what files have changed
  2. Run git diff to review the changes
  3. Stage the appropriate files with git add
  4. Create a commit with a clear, descriptive message following conventional commits format
  5. Push to the remote branch (create remote branch if needed with -u origin <branch>)
  6. Create a Pull Request using gh pr create with:
    • A clear title summarizing the changes
    • A description with:
      • Summary of what changed and why
      • Any testing done
      • Any notes for reviewers

If there are any issues at any step, stop and report them.

Download now (ZIP)

  • Other versions22 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 1

    1. galacean/effects-runtime★ 75128% same

    Wrote their own version · 21

    1. llama-farm/llamafarm★ 837same name
    2. shenjingnan/xiaozhi-client★ 341same name
    3. converge-ai-labs/agent-foundation★ 247same name
    4. RedWoodOG/Hermes-Desktop★ 177same name
    5. jh941213/ADLC-harness★ 125same name
    6. jh941213/my-cc-harness★ 125same name
    7. jh941213/my-claude-code-asset★ 125same name
    8. sneg55/agent-starter★ 76same name
    9. jackson-video-resources/skills★ 17same name
    10. shenjingnan/agentmote★ 9same name

    11 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects 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

    • xfstudioSkill

      fastapi-templates

      Create production-ready FastAPI projects with async patterns, dependency injection, and comprehensive error handling. Use when building new FastAPI applications or setting up backend API projects.

      Also in 3 projects that use this

    • +4 more from jh941213
  • In this repository8 other files it gives its agents.

Does it work?

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

Reviews can't be read right now.

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.