PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
The GitHub mechanics of this repository — building and re-rooting a gh stack, why CI runs on the bottom PR alone, which hash is stable after a merge, and how an umbrella issue closes.
Install Stacks And Issues
$ npx skills add stylelint-stylistic/stylelint-stylistic --skill stacks-and-issues -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install stylelint-stylistic/stylelint-stylistic stacks-and-issues --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/stylelint-stylistic/stylelint-stylistic.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/stacks-and-issues .claude/skills/stacks-and-issues && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "stacks-and-issues" agent skill from https://github.com/stylelint-stylistic/stylelint-stylistic/tree/main/.agents/skills/stacks-and-issues into .claude/skills/stacks-and-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stacks-and-issues", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/stylelint-stylistic/stylelint-stylistic/tree/main/.agents/skills/stacks-and-issuesType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add stylelint-stylistic/stylelint-stylistic --skill stacks-and-issues -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install stylelint-stylistic/stylelint-stylistic stacks-and-issues --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/stylelint-stylistic/stylelint-stylistic.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/stacks-and-issues .agents/skills/stacks-and-issues && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "stacks-and-issues" agent skill from https://github.com/stylelint-stylistic/stylelint-stylistic/tree/main/.agents/skills/stacks-and-issues into .agents/skills/stacks-and-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stacks-and-issues", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add stylelint-stylistic/stylelint-stylistic --skill stacks-and-issues -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install stylelint-stylistic/stylelint-stylistic stacks-and-issues --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/stylelint-stylistic/stylelint-stylistic.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/stacks-and-issues .cursor/skills/stacks-and-issues && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "stacks-and-issues" agent skill from https://github.com/stylelint-stylistic/stylelint-stylistic/tree/main/.agents/skills/stacks-and-issues into .cursor/skills/stacks-and-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stacks-and-issues", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/stylelint-stylistic/stylelint-stylistic.git --path .agents/skills/stacks-and-issues--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add stylelint-stylistic/stylelint-stylistic --skill stacks-and-issues -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install stylelint-stylistic/stylelint-stylistic stacks-and-issues --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/stylelint-stylistic/stylelint-stylistic.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/stacks-and-issues .gemini/skills/stacks-and-issues && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "stacks-and-issues" agent skill from https://github.com/stylelint-stylistic/stylelint-stylistic/tree/main/.agents/skills/stacks-and-issues into .gemini/skills/stacks-and-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stacks-and-issues", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install stylelint-stylistic/stylelint-stylistic stacks-and-issuesInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add stylelint-stylistic/stylelint-stylistic --skill stacks-and-issues -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/stylelint-stylistic/stylelint-stylistic.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/stacks-and-issues .github/skills/stacks-and-issues && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "stacks-and-issues" agent skill from https://github.com/stylelint-stylistic/stylelint-stylistic/tree/main/.agents/skills/stacks-and-issues into .github/skills/stacks-and-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stacks-and-issues", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add stylelint-stylistic/stylelint-stylistic --skill stacks-and-issues -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install stylelint-stylistic/stylelint-stylistic stacks-and-issues --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/stylelint-stylistic/stylelint-stylistic.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/stacks-and-issues .opencode/skills/stacks-and-issues && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "stacks-and-issues" agent skill from https://github.com/stylelint-stylistic/stylelint-stylistic/tree/main/.agents/skills/stacks-and-issues into .opencode/skills/stacks-and-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stacks-and-issues", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
stacks-and-issues- GitHub stars
- 106
- Token cost
- ~1.5k tokens
- SKILL.md length
- 924 words
- Files
- 1
- Skills in repo
- 6
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
The GitHub mechanics of this repository — building and re-rooting a gh stack, why CI runs on the bottom PR alone, which hash is stable after a merge, and how an umbrella issue closes.
- Reshaping a stack of pull requests
- SKILL.md covers gh stack in this repository, Which hash is stable and Umbrella issues
- Calls gh, git and make
- Quoting a merge commit
What it does
Stacks And Issues is an agent skill from stylelint-stylistic/stylelint-stylistic. The GitHub mechanics of this repository — building and re-rooting a gh stack, why CI runs on the bottom PR alone, which hash is stable after a merge, and how an umbrella issue closes. Use when creating or reshaping a stack of pull requests, quoting a merge commit, or closing an issue that stands for several others.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Pull requests. It works with GitHub. The repository describes itself as: A collection of stylistic rules for Stylelintin in a form of a plugin.
When your agent uses it
- Reshaping a stack of pull requests
- Quoting a merge commit
- Closing an issue that stands for several others
Example prompts
- “/stacks-and-issues”
What it can do on your machine
Read from SKILL.md and the folder at commit e74a1ee. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
ghgitmake
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh and git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Stacks And Issues loads about 1.5k tokens when it runs. Until then it costs about 84 tokens; SKILL.md has 924 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 924 words (~1,496 tokens).
“Stacked PRs are enabled on stylelint-stylistic/stylelint-stylistic and the github/gh-stack extension is installed. git config remote.pushDefault origin is set locally and kept as insurance: checkout, modify and trunk have no --remote flag, so a second remote appearing would break them outright…”
- name
- stacks-and-issues
Files
Just SKILL.md in .agents/skills/stacks-and-issues of stylelint-stylistic/stylelint-stylistic.
Open the folder on GitHubat commit e74a1ee
Compare with similar skills
Stacks And Issues next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Stacks And Issues this skillstylelint-stylistic/stylelint-stylistic | 106 | — | ~1.5k | Automated safety check: Pass | Custom licence | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Check PRonyx-dot-app/onyx | 32k | 2 repos | ~2.3k | Automated safety check: Pass | MIT | |
| Contributor-First PR MergeHKUDS/OpenHarness | 16k | 1 repos | ~847 | Automated safety check: Pass | MIT | |
| Create Pull Requestcline/cline | 70k | 1 repos | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| Pull Request Title and Body Writeropeninterpreter/openinterpreter | 69k | 2 repos | ~1.1k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Check PR
onyx-dot-app/onyx
Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.
Contributor-First PR Merge
HKUDS/OpenHarness
Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.
Create Pull Request
cline/cline
Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.
Pull Request Title and Body Writer
openinterpreter/openinterpreter
Rewrites the title and body of one or more pull requests with gh, leading with why the change was made, then what changed, and describing only the net result.
- Official
GitHub Review Iteration
prisma/orm
Runs a loop on a GitHub pull request: fetch review state, triage comments into actions, implement them and resolve threads, repeating until nothing actionable is left.
More from stylelint-stylistic/stylelint-stylistic
Base Comparison
stylelint-stylistic/stylelint-stylistic
Measure a branch against the commit it stands on — extract the base instead of flipping the working tree, pick the base by hash, and prove a new test case red on it.
Engine Probes
stylelint-stylistic/stylelint-stylistic
Ask a real engine what a stylesheet means instead of reasoning about tokens — the Less compiler, lightningcss, dart-sass, and a custom syntax's own parser.
History Rewriting
stylelint-stylistic/stylelint-stylistic
Fold fixups into a branch without losing a message, a marker or somebody else's branch — the amend!
Outward Prose
stylelint-stylistic/stylelint-stylistic
Write a commit body, a changelog entry, a PR body, an issue comment or a code comment so that no sentence in it is a claim nobody ran.
Sweeps And Oracles
stylelint-stylistic/stylelint-stylistic
Build a corpus that can see the change, and read what the oracles and sweeps report without over-reading it.
Related
Works with
Categories
Questions about Stacks And Issues
What does Stacks And Issues do?
The GitHub mechanics of this repository — building and re-rooting a gh stack, why CI runs on the bottom PR alone, which hash is stable after a merge, and how an umbrella issue closes. Stacks And Issues is an agent skill from stylelint-stylistic/stylelint-stylistic. The GitHub mechanics of this repository — building and re-rooting a gh stack, why CI runs on the bottom PR alone, which hash is stable after a merge, and how an umbrella issue closes.
When should I use Stacks And Issues?
Stacks And Issues fits situations like: reshaping a stack of pull requests; quoting a merge commit; closing an issue that stands for several others.
How do I install Stacks And Issues in Claude Code?
Run `npx skills add stylelint-stylistic/stylelint-stylistic --skill stacks-and-issues -a claude-code`. Or copy the skill folder (.agents/skills/stacks-and-issues in stylelint-stylistic/stylelint-stylistic) into .claude/skills/stacks-and-issues in your project. Claude Code loads it when a task matches its description.
How do I install Stacks And Issues in Codex?
Run `npx skills add stylelint-stylistic/stylelint-stylistic --skill stacks-and-issues -a codex`. Or copy the skill folder (.agents/skills/stacks-and-issues in stylelint-stylistic/stylelint-stylistic) into .agents/skills/stacks-and-issues in your project. Codex loads it when a task matches its description.
Can I use Stacks And Issues in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add stylelint-stylistic/stylelint-stylistic --skill stacks-and-issues -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/stacks-and-issues, .gemini/skills/stacks-and-issues, .github/skills/stacks-and-issues and .opencode/skills/stacks-and-issues in your project.
What does Stacks And Issues need to run?
Going by SKILL.md and its folder, Stacks And Issues needs the command-line tools its instructions call (gh, git and make).
Does Stacks And Issues access the network?
SKILL.md contains no URLs. Its commands use gh and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Stacks And Issues safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Stacks And Issues use?
Stacks And Issues has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Stacks And Issues use?
About 1.5k tokens (SKILL.md is roughly 6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Stacks And Issues?
Skills that share tags, products or a category with Stacks And Issues: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars), Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars) and Create Pull Request (cline/cline, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Stacks And Issues?
stylelint-stylistic (a GitHub organization) maintains it in stylelint-stylistic/stylelint-stylistic, which has 106 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 5, 2026.
Source: stylelint-stylistic/stylelint-stylistic on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.