// Review all README.md files in the repo for typos, errors, and outdated information. Use when the user asks to review READMEs, check documentation accuracy, or audit docs.
| name | review-readmes |
| description | Review all README.md files in the repo for typos, errors, and outdated information. Use when the user asks to review READMEs, check documentation accuracy, or audit docs. |
Audit every README.md in the repository for language quality and factual
accuracy against the current codebase.
Find all README files:
find . -name 'README.md' -not -path '*/node_modules/*'
Read each file in full.
For each README, look for:
Verify that claims in the READMEs still hold by checking the actual code. Do not guess — confirm every claim against the source.
Apply all fixes directly to the README files. For each file, briefly summarize what was changed and why.
Review a pull request for code quality, correctness, and project conventions. Use when the user asks to review a PR, code review, or examine changes on a branch. Accepts a GitHub PR URL, PR number, or local branch name.
Rebase the current branch onto its base branch, resolve all conflicts, and verify lint, i18n, and build pass. Use when the user asks to rebase, update, or sync a branch with its upstream base.
Backport commits or PRs from main to a release branch. Use when the user asks to backport, cherry-pick, or port changes between branches, or when resolving conflicts from a cherry-pick onto a release branch.
Bump the project version across all release branches and commit the changes. Use when the user asks to do a release or update the version on all branches.
Review project AI skills for duplication, stale references, mistakes, and structural issues. Use when the user asks to review skills, audit skills, check for duplicate skills, or verify skill quality.
Review CSS for coding style, PatternFly token usage, and best practices. Use when the user asks to review CSS, check styles, or audit CSS files.