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
In this repository22 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- archeoSkill
- auditSkill
- before-editSkill
- boundary-probeSkill
- check-my-workSkill
- cqs-batchSkill
- cqs-bootstrapSkill
- cqs-planSkill
- cqsSkill
- cqs-verifySkill
- docs-reviewSkill
- groom-notesSkill
- idleSkill
- investigateSkill
- landSkill
- migrateSkill
- recall-gateSkill
- reindexSkill
- releaseSkill
- troubleshootSkill
- update-tearsSkill
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
- Distinctive: line 10
Create a PR from the current branch using WSL-safe patterns.
- Distinctive: line 20
If uncommitted changes exist, ask user whether to commit first
- Very specific: line 39
Clean up: Delete pr_body.md
≈ “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.
Files
Create Pull Request
Create a PR from the current branch using WSL-safe patterns.
Process
- Check state:
git status— note any uncommitted changesgit log main..HEAD— review commits to includegit diff main...HEAD --stat— files changed
- 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'
- 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 - Create PR via PowerShell:
powershell.exe -Command 'cd C:\Projects\cqs; gh pr create --title "..." --body-file pr_body.md' - Clean up: Delete
pr_body.md - Wait for CI — pin the run ID (
gh pr checks --watchlatches 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' - Report: Show PR URL
Critical rules
- ALWAYS use
--body-file— never inline heredocs ingh pr create --body - Heredocs get captured as permission entries in
settings.local.json, corrupting startup git pushworks directly from WSL (credential helper wired); PowerShell is the fallback when GCM crashes. Allghcommands still go through PowerShell (withcd C:\Projects\cqsor-R jamie8johnson/cqs)- main is protected — all changes require PR
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
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.

