open-pr
Skill52 starsChanged 47 days agoApache-2.0View on GitHub
Prepare and open a skforecast-ai pull request against the current release branch, after running the tests and checks that CI does not run on release branches.
- Commits and pushes
67 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- gmunaro/claude-skillstheir own version, first seen Nov 16, 2026
- mazzsva/claude-skillstheir own version, first seen Nov 16, 2026
- skillberry-ai/cap-evolvetheir own version, first seen Nov 15, 2026
- eduardokairalla1/personal-skillstheir own version, first seen Nov 15, 2026
- lucasalencar/skillstheir own version, first seen Nov 15, 2026
- jameswyse/skillstheir own version, first seen Nov 15, 2026
Used with
Projects with it also use review-change, commit-push and 10 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.
thlaureSkillreview-change
Use this skill when the user asks for a code review, a correctness pass, a check before PR, or asks whether a Signalist change follows project conventions.
Also in 4 projects that use this
DataCoveySkillcommit-push
Commit and push the changes made on this chat session to the current branch. Use best practices from Conventional Commits.
Also in 3 projects that use this
Codagent-AISkillimplement-change
Implements an approved change in one continuous session, with tiered test runs. Use when asked to implement a change from its approved definition, or to invoke codagent:implement-change.
Also in 3 projects that use this
saffron-healthSkilladdress-review
Address PR review comments systematically. Use when responding to code review feedback on a pull request.
Also in 3 projects that use this
DockerSkillreview-pr
Review one or more incoming Docker documentation pull requests as a maintainer. Independently validate technical claims, assess editorial fit and information architecture, choose a verdict, and draft exact inline or PR-wide feedback behind a confirmation gate. Use for requests such as "review PR 123", "is this PR correct?", "does this information belong here?", "validate this PR", or "help review backlog PRs". Do not use to maintain or fix a PR you own; use maintain-pr for that.
Also in 10 projects that use this
SentrySkillwrite-tests
Write tests following project conventions. Use when adding new tests or modifying existing ones.
Also in 4 projects that use this
Other versions67 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- skforecast/skforecast★ 1.5k42% same
Wrote their own version · 66
- Significant-Gravitas/AutoGPT★ 188ksame name
- storybookjs/storybook★ 92ksame name
- pascalorg/editor★ 26ksame name
- dask/dask★ 14ksame name
- polarsource/polar★ 10ksame name
- cloudflare/agents★ 6ksame name
- Kiln-AI/Kiln★ 5.3ksame name
- analogjs/analog★ 3.2ksame name
- raine/workmux★ 3ksame name
- Akylas/OSS-DocumentScanner★ 2.7ksame name
56 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.
In this repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- handoffSkill
- llm-context-changeSkill
- release-bumpSkill
- release-noteSkill
- sync-skforecast-assetsSkill
- verifySkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 1 is distinctive, and 6 are very specific to this project.
0
Common
Most of the 66 edited versions we read keep these.
1
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
- Very specific: line 20
If the current branch is main or the release branch, create <type>/<slug> from BASE first (type feature, fix, docs, chore or perf, the …
- Very specific: line 32
If the branch is behind BASE, say so.
- Very specific: line 46
Run /verify on the whole branch: its scope is git diff --name-only BASE...HEAD plus the working tree, not only the last commit.
- Very specific: line 49
If the branch touches the paths of the AI context check, run what CI runs, with the Python command of /verify (the second one needs network …
- Very specific: line 59
If the branch changes what the LLM receives (llm/context.py, llm/prompts.py, skforecast_ai/skills/, recommendation/explanation.py, …
- Distinctive: line 91
Write the body to a file in the scratchpad:
- Very specific: line 112
Add the link of the new PR to its release note entries, (#123) at the end of each one (see the trailers in /release-note), then commit and …
“Common” is measured: kept by at least 6 in 10 of the 66 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.
Files
Open a pull request
Title hint from the user: $ARGUMENTS
1. Branches
- Release branch: read
__version__inskforecast_ai/__init__.pyand deriveX.Y.x(0.4.0->0.4.x). Onmain, which keeps the previous release, it is the highestX.Y.xonorigininstead. The PR base is that branch, nevermain. git fetch originand compare againstorigin/<release-branch>: the local copy of the release branch may be stale. Below,BASEstands fororigin/<release-branch>.- If the current branch is
mainor the release branch, create<type>/<slug>fromBASEfirst (typefeature,fix,docs,choreorperf, the names the cloud hook accepts). If it is aclaude/...(cloud session) orworktree-...branch, rename it withgit branch -m <type>/<slug>after checking thatgit log --oneline BASE..HEADlists only the commits of this work: a pull request keeps the name of its branch, and the Bash guard blocks pushing those. - Review
git log --oneline BASE..HEAD,git diff BASE...HEAD --statandgit status. Commit the uncommitted changes that belong to the PR without asking; leave the rest out (see thedev/files in step 2) and list them in the report. - If the branch is behind
BASE, say so; do not rebase or merge without asking. gh pr viewtells whether the branch already has a PR. If it does, update that one (push, thengh pr editif the body must change) instead of opening a second one.
2. Checks
CI runs lint and the unit tests only on pull requests to main. On a
release branch it only runs the AI context check, and only when
skforecast_ai/skills/, skforecast_ai/resources/ or
skforecast_ai/llm/prompts.py change. The checks run here are the only
ones before merge.
- Run
/verifyon the whole branch: its scope isgit diff --name-only BASE...HEADplus the working tree, not only the last commit. Stop on failures. - If the branch touches the paths of the AI context check, run what CI
runs, with the Python command of
/verify(the second one needs network access):
Changes topython tools/ai/measure_skill_tokens.py --check python tools/ai/sync_skforecast_assets.py --check --branch autoskforecast_ai/skills/orskforecast_ai/resources/llms-base.txtmust come from the sync script, never from a hand edit. - If the branch changes what the LLM receives (
llm/context.py,llm/prompts.py,skforecast_ai/skills/,recommendation/explanation.py,execution/backtesting_runner.py,execution/comparison.py), the goldens must be regenerated on purpose (/llm-context-change). The real-model run oftools/ai/check_ask_context.pycosts money, so the user launches it: ask whether it was run and whether its report is saved undertools/ai/ask_context_reports/; otherwise list it as pending in the PR body. - User-facing changes (API, CLI output, generated scripts, warnings) have
an entry in
docs/releases/releases.mdunder the version in development, as short entries (one or two sentences; the detail goes in the PR description). If one is missing or over the length ceiling (python tools/docs/check_release_notes.py), follow/release-noteand show the result to the user. dev/holds working notes. Nodev/handoff_*.mdfile (written by/handoff) is part of the PR: delete it first, asking the user. The other notes are versioned only on purpose (dev/roadmap-0.6.0.md): list thedev/files in the diff and ask whether each belongs to the PR.
3. Open the PR
- GitHub account:
git remote -vshows which account pushes (an SSH host alias may point to a different key thanghuses), andgh api user --jq .loginshows which accountghwould open the PR with. If they are not the same person, stop and ask: the user can switch withgh auth switch(or log in the other account withgh auth login), or open the PR from the link printed bygit push. Never switch accounts yourself. - Push the branch with
git push -u origin <branch>(a local session asks for confirmation; the Bash guard blocks pushes tomain). - Write the body to a file in the scratchpad:
- Maintainers (Javier Escobar Ortiz, Joaquin Amat Rodrigo, as in
pyproject.toml; compare withgit config user.name): a## Descriptionof what changes and why (link the issue if any) and a## How was this tested?section listing each check run, with its command and result (number of tests passed), plus what was not run (for example the real-modelcheck_ask_context.pyrun). Leave out the checklist of.github/pull_request_template.md: it is written for external contributors (the CLA does not apply to the copyright holders), and the results say more than ticked boxes. The## Descriptioncarries the technical detail that the release note leaves out: the cause of a bug, how it was fixed, the measurements and the edge cases. - Anyone else: fill
.github/pull_request_template.mdwith the Description, how it was tested and the checklist, ticking only what was actually verified.
- Maintainers (Javier Escobar Ortiz, Joaquin Amat Rodrigo, as in
- Create it with
gh pr create --base <release-branch> --title "<title>" --body-file <file>. The title follows the commit style of the repository (fix(forecast): ...,docs(dev): ...). In a cloud session, use the session's PR flow ifghis not authenticated. - Add the link of the new PR to its release note entries,
([#123](https://github.com/skforecast/skforecast-ai/pull/123))at the end of each one (see the trailers in/release-note), then commit and push that change to the same branch. - The title, body and commits carry only the author's identity: no AI
co-author trailer, session link, "Generated with" or "Generated by"
line or mention of Claude (the Bash guard blocks them, also in a
--body-file, and so does the guard of the GitHub MCP tools). In a cloud session the GitHub MCP server appends a "Generated by Claude Code" footer after the call: read the new pull request back and remove it with the update tool (a hook reminds you). No en dashes or em dashes.
4. Report
Give the PR URL, the checks run with their results, and anything left for
the reviewer (pending real-model run, dev/ files left out, open
questions).
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.

