본문으로 건너뛰기
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.

storybookjs/storybook
연동 도구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(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

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 / 1,000자

이 양식은 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일 업데이트

component-docs

무료

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일 업데이트

docs-review

무료

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일 업데이트

github-qa-labels

무료

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일 업데이트

handle-pr-comments

무료

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의 스킬 모두 보기

이 스킬의 문제 신고