Check out a GitHub pull request, fix linting and TypeScript errors, and commit and push the changes. The workflow supports forked pull requests and repeats type checks to verify fixes while keeping changes focused on these errors.
Checks out a PR (including fork PRs), fixes all linting and TypeScript errors, then pushes the changes back. Use when asked to fix lint, types, or TS errors on a PR.
Review the instructions the agent will receive before you install.
Checks out a PR, auto-fixes linting and TypeScript issues, and pushes the fixes.
If the user provided a PR number, use it directly. Otherwise ask for it.
Use gh pr checkout so it works for both fork and non-fork PRs:
gh pr checkout <PR_NUMBER>
This automatically sets up the correct remote tracking and switches to the PR branch, even when the PR comes from a fork.
yarn
Compiling first ensures TS declarations referenced by the linter are present:
yarn nx run-many -t compile
yarn lint
Run the TypeScript checker to surface remaining type errors:
yarn nx run-many -t check
Read the output carefully. Fix each type error manually by editing the relevant file(s). Common fixes:
any assignments that violate strict modeRe-run yarn nx run-many -t check after each batch of edits to confirm errors are resolved.
Stage only the files you changed:
git add <files-you-modified>
git commit -m "Maintenance: Fix linting and TypeScript errors"
Do not use git add -A — avoid accidentally staging unrelated files.
For fork PRs gh pr checkout sets up the correct upstream tracking. Push directly:
git push
gh pr checkout fails due to permissions on a fork, inform the user — they may need to grant write access to the fork or the maintainer must push directly.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Find a trial Storybook package for a specific branch, or trigger its publication when needed. Check release progress and obtain the package reference or commands for creating or upgrading a project with that build.
Look up a project's existing UI components in Storybook, including their props, or configuration inputs, and usage examples. Use the findings to answer questions and identify components to reuse before building duplicates.
Review, improve, rewrite, or draft Storybook documentation in /docs. Assess each page’s purpose, audience, structure, and examples, then make suitable edits or provide a content plan, with formatting checks after changes.
Organize GitHub issues and pull requests found during quality assurance testing. Apply release tracking labels, classify bugs by four severity levels, and label multiple findings while keeping documentation issues and feature requests outside the severity scheme.
Work through unresolved GitHub pull request reviews one at a time. The skill explains each comment, proposes a fix, asks how to proceed, and handles chosen edits, replies, commits, and thread resolution.
Add Storybook to a project that does not have it configured, choosing the installation tag based on the latest stable version. Then use the separate setup skill to configure Storybook for the project.