跳到正文
cccskills
免费在 GitHub 公开

fix-linting-types-on-pr

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.

集成工具GitHub
查看安装方法

适用场景

  • Fix linting errors in a pull request
  • Resolve TypeScript errors in a pull request
  • Apply fixes to a pull request from a fork
  • Commit and push verified lint and type fixes

包含的文件(1)

  • SKILL.md2.2 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Fix Linting and TypeScript Issues on a PR

Checks out a PR, auto-fixes linting and TypeScript issues, and pushes the fixes.

Step 1 — Get the PR number

If the user provided a PR number, use it directly. Otherwise ask for it.

Step 2 — Check out the PR

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.

Step 3 — Install dependencies

yarn

Step 4 — Compile the repo

Compiling first ensures TS declarations referenced by the linter are present:

yarn nx run-many -t compile

Step 5 — Fix linting errors

yarn lint

Step 6 — Fix TypeScript errors

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:

  • Add or correct type annotations
  • Fix incorrect generics
  • Resolve any assignments that violate strict mode
  • Add missing imports or re-exports

Re-run yarn nx run-many -t check after each batch of edits to confirm errors are resolved.

Step 7 — Commit the fixes

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.

Step 8 — Push the fixes

For fork PRs gh pr checkout sets up the correct upstream tracking. Push directly:

git push

Notes

  • Only fix errors that are clearly linting or TypeScript issues. Do not refactor logic.
  • If a TypeScript error requires a non-trivial code change, surface it to the user and ask before proceeding.
  • If 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.
  • After pushing, confirm with the user that the CI is green.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

canary

免费

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.

中文简介正在准备中。当前显示英语简介。

  • Find a trial package for a Storybook branch
  • Publish a trial build for a fork pull request
  • Check publication progress and installation commands
storybookjs/storybook9.1万2026年10月18日 更新

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.

中文简介正在准备中。当前显示英语简介。

  • Find existing UI components
  • Check component props and usage examples
  • Answer questions about component usage
storybookjs/storybook9.1万2026年10月18日 更新

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.

中文简介正在准备中。当前显示英语简介。

  • Improve the structure and examples of a documentation page
  • Draft documentation for a new feature
  • Plan page types and outlines
storybookjs/storybook9.1万2026年10月18日 更新

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.

中文简介正在准备中。当前显示英语简介。

  • Group QA findings by release
  • Classify bugs by severity
  • Apply labels to multiple issues and pull requests
storybookjs/storybook9.1万2026年10月18日 更新

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.

中文简介正在准备中。当前显示英语简介。

  • Addressing unresolved pull request review comments
  • Choosing between a code fix, a reply, or skipping a comment
  • Handling duplicate review comments together
storybookjs/storybook9.1万2026年10月18日 更新

init

免费

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.

中文简介正在准备中。当前显示英语简介。

  • Adding Storybook to a project for the first time
  • Choosing an installation tag based on the stable release
  • Continuing from installation to project-specific setup
storybookjs/storybook9.1万2026年10月18日 更新

查看 storybookjs 的全部技能

报告此技能的问题