본문으로 건너뛰기
cccskills
무료GitHub에 공개

pr

Prepare and publish a pull request with a linked issue, English commit and PR titles, and a Chinese description explaining the change, implementation, and verification. Update an existing branch PR and report its URL and CI status.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

Open or update a pull request in this repository, including writing or rewriting its description. Use for every PR you create or edit here, and for /pr.

연동 도구GitHub
설치 방법 보기

이럴 때 유용합니다

  • Publishing current code changes as a pull request
  • Rewriting a PR description to match the final changes
  • Adding diagrams and rendered terminal output to a PR
  • Linking issues and reporting verification and CI status

포함된 파일(1)

  • SKILL.md2.4 KB

SKILL.md(원문)

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

Ship the current change as a pull request a reviewer can understand from the description alone: why it exists, the shape of the implementation, and what was actually verified.

  1. Make sure a code PR has a closing issue: the issue-link CI check fails one without it. Docs-only PRs and PRs a maintainer labels no-issue-needed are exempt (docs/contributing.md). Reuse the issue the work came from; when there is none, open a tracking issue first — title [功能]/[Bug] …, body with 目标, 范围, and 非目标 sections, as in #919 — and link it.
  2. Commit and push. Title the commit and the PR in English, type(scope): summary (conventional commits, as in #1110); the commit body is English too. Stage explicit paths only, leave lib/ and unrelated worktree changes out, and push a branch whose upstream is itself, never main. Reuse the PR already open for the branch (gh pr view) instead of opening a second one.
  3. Read the complete diff against the base, the linked issue, and enough surrounding code to explain ownership and behavior. Collect the verification you actually ran; run what docs/contributing.md requires for the changed area when it has not run yet.
  4. Write the body from .github/PULL_REQUEST_TEMPLATE.md, following the HTML comments in it and then deleting them:
    • Why the change is exactly one sentence.
    • Special things to note holds 1–3 reviewer warnings; deliberate divergences, omissions, and unrun checks go here.
    • Change outline is a visual outline, not prose or a file-by-file changelog: the smallest set of views — file tree, call or data flow, key shapes — each beside one short sentence, diff for a changed shape and a full block for a new one. For a terminal-visible change include the real rendered screen as a text block, captured headlessly the way the scripts/verify-*.tsx regressions render (renderToScreen or an @xterm/headless terminal).
    • Verification lists the commands that ran and their results. Write the body in Chinese, plainly, one person to another.
  5. Publish with gh pr create --body-file or gh pr edit --body-file, then confirm the rendered body with gh pr view. Report the PR URL, the linked issue, and the CI state.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

audit

무료

Audit a repository or broad subsystem for security, correctness, and maintenance risks. Trace how inputs reach affected behavior, verify suspected defects, and report confirmed findings with severity, triggers, impact, and practical remedies.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Auditing risks across a repository
  • Checking state loss and resource limits in a TUI
  • Checking dependencies for known vulnerabilities
ccch1mneyyy/dsh-TUI5천2026년 10월 19일 업데이트

bug

무료

Turn a reported defect into a concise bug report or issue draft that someone else can reproduce or investigate. Organize symptoms, reproduction steps, expected and actual behavior, environment, and impact while separating evidence from unknowns.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Turning a defect description into a bug report
  • Organizing reproduction steps and expected behavior
  • Adding evidence from logs and relevant code
ccch1mneyyy/dsh-TUI5천2026년 10월 19일 업데이트

Answer questions about dsh-tui using its bundled manuals. Find relevant guidance on installation, shortcuts, configuration, themes, session migration, and VS Code integration, then cite the source file and section for checking.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Looking up shortcuts and everyday operations
  • Checking configuration and theme settings
  • Finding guidance for migrating sessions
ccch1mneyyy/dsh-TUI5천2026년 10월 19일 업데이트

Turn existing pull request review comments into prioritized next steps by checking them against the current code. Separate outstanding concerns, addressed feedback, and questions needing replies, then implement and validate fixes when requested.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Prioritizing pull request review feedback
  • Checking whether comments still apply to current code
  • Implementing and validating requested review fixes
ccch1mneyyy/dsh-TUI5천2026년 10월 19일 업데이트

practice

무료

Practice one programming concept through a small exercise matched to your goals, experience, and available time. Get feedback based on observable results, with hints or explained solutions and a harder variation when you are ready.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Practicing a programming concept in 10–15 minutes
  • Understanding display width for CJK characters and emoji
  • Tracing event order and cleanup
ccch1mneyyy/dsh-TUI5천2026년 10월 19일 업데이트

Draft release notes that explain what changes for users. Verify the release range, reconcile commits and reversals, and highlight breaking changes, migration steps, and relevant pull requests with evidence.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Drafting release notes for a specific version
  • Explaining breaking changes and migration steps
  • Summarizing user-visible changes across pull requests
ccch1mneyyy/dsh-TUI5천2026년 10월 19일 업데이트

ccch1mneyyy의 스킬 모두 보기

이 스킬의 문제 신고