CI Act Run
chewiebug/GCViewer
Run the full build-and-deploy.yaml workflow locally via act + Docker.
Maintain and follow up on a single Docker documentation pull request that you own or are responsible for updating.
Install Maintain PR
$ npx skills add docker/docs --skill maintain-pr -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install docker/docs maintain-pr --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/docker/docs.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/maintain-pr .claude/skills/maintain-pr && 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 "maintain-pr" agent skill from https://github.com/docker/docs/tree/main/.agents/skills/maintain-pr into .claude/skills/maintain-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maintain-pr", 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/docker/docs/tree/main/.agents/skills/maintain-prType 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 docker/docs --skill maintain-pr -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install docker/docs maintain-pr --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/docker/docs.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/maintain-pr .agents/skills/maintain-pr && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "maintain-pr" agent skill from https://github.com/docker/docs/tree/main/.agents/skills/maintain-pr into .agents/skills/maintain-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maintain-pr", 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 docker/docs --skill maintain-pr -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install docker/docs maintain-pr --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/docker/docs.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/maintain-pr .cursor/skills/maintain-pr && 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 "maintain-pr" agent skill from https://github.com/docker/docs/tree/main/.agents/skills/maintain-pr into .cursor/skills/maintain-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maintain-pr", 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/docker/docs.git --path .agents/skills/maintain-pr--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 docker/docs --skill maintain-pr -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install docker/docs maintain-pr --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/docker/docs.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/maintain-pr .gemini/skills/maintain-pr && 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 "maintain-pr" agent skill from https://github.com/docker/docs/tree/main/.agents/skills/maintain-pr into .gemini/skills/maintain-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maintain-pr", 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 docker/docs maintain-prInstalls 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 docker/docs --skill maintain-pr -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/docker/docs.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/maintain-pr .github/skills/maintain-pr && 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 "maintain-pr" agent skill from https://github.com/docker/docs/tree/main/.agents/skills/maintain-pr into .github/skills/maintain-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maintain-pr", 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 docker/docs --skill maintain-pr -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install docker/docs maintain-pr --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/docker/docs.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/maintain-pr .opencode/skills/maintain-pr && 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 "maintain-pr" agent skill from https://github.com/docker/docs/tree/main/.agents/skills/maintain-pr into .opencode/skills/maintain-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maintain-pr", 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
maintain-pr- GitHub stars
- 4.7k
- Token cost
- ~825 tokens
- SKILL.md length
- 319 words
- Files
- 2
- Skills in repo
- 13
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Maintain and follow up on a single Docker documentation pull request that you own or are responsible for updating.
- Works in 5 steps: Gather PR state → Handle terminal states → Diagnose CI failures → …
- Requests such as babysit this PR
- SKILL.md covers 1. Gather PR state, 2. Handle terminal states, 3. Diagnose CI failures and 4. Address review feedback, plus 1 more section
- Calls gh
What it does
Maintain PR is an agent skill from docker/docs, published by the product's own GitHub organization. Maintain and follow up on a single Docker documentation pull request that you own or are responsible for updating. Check CI and review feedback, fix actionable failures, push changes, reply to comments, and report status. Use for requests such as "babysit this PR", "check the status of my PR", "fix CI on my PR", or "address review comments on 500". Do not use for maintainer review of an incoming contribution; use review-pr for that.
Its SKILL.md is about 830 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
It sits in Development, covering Pull requests, Failing and flaky tests and Containers. It works with Docker. The repository describes itself as: Source repo for Docker's Documentation. The licence is Apache-2.0.
When your agent uses it
- Requests such as babysit this PR
- Check the status of my PR
- Fix CI on my PR
- Address review comments on 500
Example prompts
- “babysit this PR”
- “check the status of my PR”
- “fix CI on my PR”
- “/maintain-pr”
Requirements
- Docker
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 65aa5cd. 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:
gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh, 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
Maintain PR loads about 825 tokens when it runs. Until then it costs about 112 tokens; SKILL.md has 319 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
The full file from docker/docs at commit 65aa5cd, republished under its Apache-2.0 licence (© docker). 319 words, ~825 tokens.
Download SKILL.mdSave it as
.claude/skills/maintain-pr/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- maintain-pr
- description
- Maintain and follow up on a single Docker documentation pull request that you own or are responsible for updating. Check CI and review feedback, fix actionable failures, push changes, reply to comments, and report status. Use for requests such as "babysit this PR", "check the status of my PR", "fix CI on my PR", or "address review comments on #500". Do not use for maintainer review of an incoming contribution; use review-pr for that.
Maintain PR
Do one maintenance pass over the specified author-owned PR: inspect its state, fix actionable failures or feedback, reply to reviewers, and report the result. This workflow may modify the branch and GitHub because the user is asking to maintain the PR. Do not apply it to an incoming PR merely because the user asks to review or assess it.
1. Gather PR state
gh pr view <PR> --repo docker/docs --json state,title,url,headRefName,headRepositoryOwner,comments,reviews,reviewDecision
gh pr checks <PR> --repo docker/docs --json name,state,detailsUrl
gh api repos/docker/docs/pulls/<PR>/comments \
--jq '[.[] | {id, author: .user.login, body, path, line, in_reply_to_id}]'Always check both top-level reviews and inline comments. A review with an
empty body may still contain line-level feedback. Confirm that the PR is one
the user owns or is authorized to update before checking out or pushing its
branch. If not, stop and use review-pr.
2. Handle terminal states
If merged, report the final state and identify unanswered review comments. Reply only when the user remains responsible for follow-up.
If closed without merge, read the closing context and report the reason. Common causes include maintainer rejection, supersession, or automation.
3. Diagnose CI failures
- Read the failure details.
- Determine whether the failure comes from the PR or predates it.
- Fix actionable failures in the PR's changed files.
- Report pre-existing or upstream failures without changing unrelated files.
Follow repository instructions for formatting, targeted linting, explicit staging, commits, and pushes. Preserve unrelated working-tree changes.
4. Address review feedback
Treat every review comment as a claim to verify. Implement it only when the evidence supports it; explain any evidence-based disagreement.
After each fix:
- Format and validate the changed files.
- Commit and push the focused change.
- Reply to every addressed thread with what changed or why no change was made.
- End replies with an accurate agent-disclosure footer, such as
Generated by Codex. - Resolve threads only after replying.
- Re-request review when appropriate.
Use the inline comment endpoint to reply:
gh api repos/docker/docs/pulls/<PR>/comments \
--method POST \
--field in_reply_to=<COMMENT_ID> \
--field body='<RESPONSE>'Use GraphQL to retrieve unresolved review-thread IDs and resolve only the threads that were addressed. Do not silently fix feedback without replying.
5. Report
## PR #<number>: <title>
**State:** <open, merged, or closed>
**CI:** <passing, failing, or pending>
**Review:** <approved, changes requested, or pending>
**Action taken:** <changes, replies, and thread resolution, or none needed>© docker, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in .agents/skills/maintain-pr of docker/docs.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit 65aa5cd
Compare with similar skills
Maintain PR 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 |
|---|---|---|---|---|---|---|
| Maintain PR this skilldocker/docs | 4.7k | — | ~825 | Automated safety check: Pass | Apache-2.0 | |
| CI Act Runchewiebug/GCViewer | 4.6k | — | ~2.4k | Automated safety check: Notes | Custom licence | |
| Review PRmicrosoft/vscode-containers | 141 | — | ~900 | Automated safety check: Pass | Custom licence | |
| ReleasePipelex/pipelex | 939 | — | ~4.8k | Automated safety check: Notes | Custom licence | |
| Debug CIweb-infra-dev/rslint | 460 | — | ~2.8k | Automated safety check: Pass | MIT | |
| Veomni ReviewByteDance-Seed/VeOmni | 2.2k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Review PR
microsoft/vscode-containers
Review a specific vscode-containers pull request on demand from the CLI (or any interactive agent), the way a Container Tools maintainer would.
Release
Pipelex/pipelex
Cut a release of pipelex, which ships the pipelex and pipelex-api packages and the pipelex/pipelex-api Docker image under one version: the gates, the migration-ledger cross-check, the CHANGELOG.md…
Debug CI
web-infra-dev/rslint
Reproduce Linux CI failures locally using Docker when the same tests pass on the host, especially Go platform differences and VS Code extension tests requiring xvfb.
Veomni Review
ByteDance-Seed/VeOmni
Pre-PR code review gate. An agent skill from ByteDance-Seed/VeOmni.
- Official
Code Review
microsoft/vscode-containers
Review a pull request in this repository (the vscode-containers / Container Tools extension) when the automated reviewer has already supplied the diff and changed files.
More from docker/docs
All 13 skills in this repo- Official
Agent Readiness Audit
docker/docs
Audit a documentation site for agent-friendliness: discovery, markdown delivery, crawlability, semantic structure, machine-readable surfaces, and content legibility.
- Official
Migrate Content Ia
docker/docs
Handle Hugo docs information-architecture moves: discover old vs new URLs, add front matter aliases (Phase 1), update in-repo links (Phase 2), interactive List 2 resolution and fragment validation…
- Official
Write
docker/docs
Write or edit reader-facing technical prose for immediate comprehension.
- Official
Create Lab Guide
docker/docs
Clone a dockersamples Labspace repo, extract learning objectives and module structure from labspace.yaml, and produce a Hugo guide page under content/guides/ with correct frontmatter…
- Official
Curate Whats New
docker/docs
Curate noteworthy Docker launches from documentation pull requests merged during a requested period.
- Official
Fix Issue
docker/docs
Fix a single GitHub issue end-to-end: triage, research, write the fix, review, and create a PR.
Related
Works with
Categories
Questions about Maintain PR
What does Maintain PR do?
Maintain and follow up on a single Docker documentation pull request that you own or are responsible for updating. Maintain PR is an agent skill from docker/docs, published by the product's own GitHub organization. Maintain and follow up on a single Docker documentation pull request that you own or are responsible for updating.
When should I use Maintain PR?
Maintain PR fits situations like: requests such as babysit this PR; check the status of my PR; fix CI on my PR; address review comments on 500.
How do I install Maintain PR in Claude Code?
Run `npx skills add docker/docs --skill maintain-pr -a claude-code`. Or copy the skill folder (.agents/skills/maintain-pr in docker/docs) into .claude/skills/maintain-pr in your project. Claude Code loads it when a task matches its description.
How do I install Maintain PR in Codex?
Run `npx skills add docker/docs --skill maintain-pr -a codex`. Or copy the skill folder (.agents/skills/maintain-pr in docker/docs) into .agents/skills/maintain-pr in your project. Codex loads it when a task matches its description.
Can I use Maintain PR 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 docker/docs --skill maintain-pr -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/maintain-pr, .gemini/skills/maintain-pr, .github/skills/maintain-pr and .opencode/skills/maintain-pr in your project.
What does Maintain PR need to run?
Going by SKILL.md and its folder, Maintain PR needs the command-line tools its instructions call (gh). Our summary lists: Docker.
Does Maintain PR access the network?
SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Maintain PR 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 Maintain PR use?
Maintain PR is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Maintain PR use?
About 825 tokens (SKILL.md is roughly 3.3k 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 Maintain PR?
Skills that share tags, products or a category with Maintain PR: CI Act Run (chewiebug/GCViewer, 4.6k stars), Review PR (microsoft/vscode-containers, 141 stars), Release (Pipelex/pipelex, 939 stars) and Debug CI (web-infra-dev/rslint, 460 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Maintain PR?
docker (a GitHub organization, an official publisher) maintains it in docker/docs, which has 4,666 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on October 7, 2026.
Source: docker/docs on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.