agentleFS
jamie8johnsonjamie8johnson/cqs/.claude/skills/pr/SKILL.md

pr

Skill18 starsChanged 5 months agoMITView on GitHub

Create a pull request with WSL-safe workflow. Uses --body-file to avoid heredoc permission corruption.

  • Commits and pushes

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    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:

    Create a PR from the current branch using WSL-safe patterns.

    line 10
  2. Distinctive:

    If uncommitted changes exist, ask user whether to commit first

    line 20
  3. Very specific:

    Clean up: Delete pr_body.md

    line 39

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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

Create Pull Request

Create a PR from the current branch using WSL-safe patterns.

Process

  1. Check state:
    • git status — note any uncommitted changes
    • git log main..HEAD — review commits to include
    • git diff main...HEAD --stat — files changed
  2. Prepare:
    • If uncommitted changes exist, ask user whether to commit first
    • Push the branch directly from WSL: git push -u origin BRANCH (the Windows credential manager is wired into WSL git). Fallback ONLY if GCM crashes ("could not read Username"): powershell.exe -Command 'cd C:\Projects\cqs; git push -u origin BRANCH'
  3. Write PR body to /mnt/c/Projects/cqs/pr_body.md:
    ## Summary
    - Bullet points summarizing changes
    
    ## Test plan
    - [ ] cargo test passes
    - [ ] cargo clippy clean
    - [ ] Manual verification steps
  4. Create PR via PowerShell:
    powershell.exe -Command 'cd C:\Projects\cqs; gh pr create --title "..." --body-file pr_body.md'
  5. Clean up: Delete pr_body.md
  6. Wait for CI — pin the run ID (gh pr checks --watch latches onto the previous commit's completed run after a push; do not use it):
    sleep 45   # new run needs ~45s to register after the push
    powershell.exe -Command 'cd C:\Projects\cqs; gh run list --branch BRANCH --workflow CI --limit 1'
    powershell.exe -Command 'cd C:\Projects\cqs; gh run watch RUN_ID --exit-status'
  7. Report: Show PR URL

Critical rules

  • ALWAYS use --body-file — never inline heredocs in gh pr create --body
  • Heredocs get captured as permission entries in settings.local.json, corrupting startup
  • git push works directly from WSL (credential helper wired); PowerShell is the fallback when GCM crashes. All gh commands still go through PowerShell (with cd C:\Projects\cqs or -R jamie8johnson/cqs)
  • main is protected — all changes require PR

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.