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.
A skill your agent uses when drafting a concise GitHub issue or discussion reply for AtomUI based on repository state, bug analysis, requested behavior, workarounds, or maintainer follow-up questions.
$ npx skills add AtomUI/AtomUI --skill issue-reply -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install AtomUI/AtomUI issue-reply --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/AtomUI/AtomUI.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/issue-reply .claude/skills/issue-reply && 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 "issue-reply" agent skill from https://github.com/AtomUI/AtomUI/tree/release%2F6.0/.agents/skills/issue-reply into .claude/skills/issue-reply/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-reply", 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/AtomUI/AtomUI/tree/release%2F6.0/.agents/skills/issue-replyType 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 AtomUI/AtomUI --skill issue-reply -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install AtomUI/AtomUI issue-reply --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AtomUI/AtomUI.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/issue-reply .agents/skills/issue-reply && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "issue-reply" agent skill from https://github.com/AtomUI/AtomUI/tree/release%2F6.0/.agents/skills/issue-reply into .agents/skills/issue-reply/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-reply", 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 AtomUI/AtomUI --skill issue-reply -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install AtomUI/AtomUI issue-reply --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AtomUI/AtomUI.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/issue-reply .cursor/skills/issue-reply && 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 "issue-reply" agent skill from https://github.com/AtomUI/AtomUI/tree/release%2F6.0/.agents/skills/issue-reply into .cursor/skills/issue-reply/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-reply", 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/AtomUI/AtomUI.git --path .agents/skills/issue-reply--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 AtomUI/AtomUI --skill issue-reply -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install AtomUI/AtomUI issue-reply --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AtomUI/AtomUI.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/issue-reply .gemini/skills/issue-reply && 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 "issue-reply" agent skill from https://github.com/AtomUI/AtomUI/tree/release%2F6.0/.agents/skills/issue-reply into .gemini/skills/issue-reply/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-reply", 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 AtomUI/AtomUI issue-replyInstalls 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 AtomUI/AtomUI --skill issue-reply -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/AtomUI/AtomUI.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/issue-reply .github/skills/issue-reply && 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 "issue-reply" agent skill from https://github.com/AtomUI/AtomUI/tree/release%2F6.0/.agents/skills/issue-reply into .github/skills/issue-reply/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-reply", 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 AtomUI/AtomUI --skill issue-reply -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install AtomUI/AtomUI issue-reply --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AtomUI/AtomUI.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/issue-reply .opencode/skills/issue-reply && 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 "issue-reply" agent skill from https://github.com/AtomUI/AtomUI/tree/release%2F6.0/.agents/skills/issue-reply into .opencode/skills/issue-reply/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-reply", 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.
issue-replyA skill your agent uses when drafting a concise GitHub issue or discussion reply for AtomUI based on repository state, bug analysis, requested behavior, workarounds, or maintainer follow-up questions.
Issue Reply is an agent skill from AtomUI/AtomUI. Use when drafting a concise GitHub issue or discussion reply for AtomUI based on repository state, bug analysis, requested behavior, workarounds, or maintainer follow-up questions.
Its SKILL.md is about 250 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. It works with GitHub. The repository describes itself as: An enhancement and extension library for Avalonia, bringing the Ant Design design language, modern controls, theming, native integrations, and cross-platform UI capabilities to… The licence is LGPL-3.0.
5 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit e82b36c. It shows what the files ask for, not the result of running them.
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.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Issue Reply loads about 249 tokens when it runs. Until then it costs about 48 tokens; SKILL.md has 114 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.
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.
The full file from AtomUI/AtomUI at commit e82b36c, republished under its LGPL-3.0 licence (© AtomUI). 114 words, ~249 tokens.
.claude/skills/issue-reply/SKILL.md (or your agent's skills folder).Use this skill to draft maintainer-quality replies for AtomUI issues or discussions.
Return a ready-to-post Markdown reply. Include commands, versions, or reproduction steps only when they are relevant.
© AtomUI, LGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .agents/skills/issue-reply of AtomUI/AtomUI.
Open the folder on GitHubat commit e82b36c
Issue Reply 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 |
|---|---|---|---|---|---|---|
| Issue Reply this skillAtomUI/AtomUI | 842 | — | ~249 | Automated safety check: Pass | LGPL-3.0 | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Greplooponyx-dot-app/onyx | 32k | 4 repos | ~3.3k | Automated safety check: Pass | MIT | |
| Check PRonyx-dot-app/onyx | 32k | 2 repos | ~2.3k | Automated safety check: Pass | MIT | |
| Setup Matt Pocock Skillsbestofjs/bestofjs | 3.1k | 20 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Summarise Ecosystem Resultsastral-sh/ruff | 50k | 1 repos | ~2.2k | Automated safety check: Pass | MIT |
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
onyx-dot-app/onyx
Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.
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.
bestofjs/bestofjs
Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout.
astral-sh/ruff
A skill your agent uses when a user says "summarise ecosystem results", "summarize this ty ecosystem report", "what changed in this ecosystem run?", or asks to summarise or summarize ty ecosystem…
HKUDS/OpenHarness
Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.
AtomUI/AtomUI
A skill your agent uses when building, launching, debugging, or visually inspecting AtomUIGallery.Desktop from an AtomUI checkout where installed or mounted Gallery apps may share its name or bundle…
AtomUI/AtomUI
Generate a single-line commit message for AtomUI by reading the project's git staged area and recent commit style.
AtomUI/AtomUI
A skill your agent uses when optimizing, refactoring, reviewing, or fixing AtomUI controls, including control API contracts, member layout, file splitting, lifecycle, AXAML structure, correctness…
AtomUI/AtomUI
A skill your agent uses when creating, completing, splitting, reviewing, or synchronizing AtomUI control documentation under docs/controls, including overview.md, implementation.md, token.md…
AtomUI/AtomUI
A skill your agent uses when changing AtomUI or Avalonia resource bindings, DynamicResource, TokenResourceBinder, non-Visual AvaloniaObject lifecycle, IResourceHost/IThemeVariantHost…
AtomUI/AtomUI
A skill your agent uses when upgrading AtomUI NuGet dependencies, source dependency projects, ReactiveUI, Avalonia, Splat, or any third-party version where compatibility must be evaluated before…
Works with
Categories
A skill your agent uses when drafting a concise GitHub issue or discussion reply for AtomUI based on repository state, bug analysis, requested behavior, workarounds, or maintainer follow-up questions. Issue Reply is an agent skill from AtomUI/AtomUI. Use when drafting a concise GitHub issue or discussion reply for AtomUI based on repository state, bug analysis, requested behavior, workarounds, or maintainer follow-up questions.
Issue Reply fits situations like: drafting a concise GitHub issue; discussion reply for AtomUI based on repository state; requested behavior; maintainer follow-up questions.
Run `npx skills add AtomUI/AtomUI --skill issue-reply -a claude-code`. Or copy the skill folder (.agents/skills/issue-reply in AtomUI/AtomUI) into .claude/skills/issue-reply in your project. Claude Code loads it when a task matches its description.
Run `npx skills add AtomUI/AtomUI --skill issue-reply -a codex`. Or copy the skill folder (.agents/skills/issue-reply in AtomUI/AtomUI) into .agents/skills/issue-reply in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add AtomUI/AtomUI --skill issue-reply -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/issue-reply, .gemini/skills/issue-reply, .github/skills/issue-reply and .opencode/skills/issue-reply in your project.
SKILL.md names no scripts, command-line tools or credentials: Issue Reply is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
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.
Issue Reply is published under the LGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 249 tokens (SKILL.md is roughly 996 characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Issue Reply: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Greploop (onyx-dot-app/onyx, 32k stars), Check PR (onyx-dot-app/onyx, 32k stars) and Setup Matt Pocock Skills (bestofjs/bestofjs, 3.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
AtomUI (a GitHub organization) maintains it in AtomUI/AtomUI, which has 842 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on October 7, 2026.
Source: AtomUI/AtomUI on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.