open-pr-upgrade
Skill45 starsChanged 3 months agoMITView on GitHub
Bring every per-repo open-pr config below the current directory up to the schema this build expects. Use after updating the plugin, or when a command reports a config too old. Takes no URL.
In this repository8 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- e2e-loopSkill
- open-pr-cleanSkill
- open-pr-feedbackSkill
- open-pr-fixSkill
- open-pr-menubarSkill
- open-pr-reviewSkill
- open-pr-watchSkill
The file
Files
Read../../adapters/root.md(relative to this file) →ROOT+ this platform's tool names.ReadROOT/commands/upgrade.md→ obey VERBATIM, every step, in order. Arguments handed to this skill are that file'sUsage:block.
FORBIDDEN: summarizing, reordering or skipping a step; migrating from what this file says; treating a tool you lack as a step you may drop.
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.