사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/t3dotgg/tstack --skill file-pr시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
File PR
Before filing, check whether a PR for this branch already exists. Review the diff locally against the base branch (usually origin/main) to make sure its contents match the goal.
PR titles usually become commit messages, so follow the repository's title conventions. Look at recently merged PRs and Git history for examples. Prefer a concise, human-readable title that explains why the change matters:
BAD
❌ perf(server): negotiate permessage-deflate on the websocket
GOOD
✅ perf(server): cut websocket frame size by 70%+ with gzipping
Open the description with a simple explanation of the problem based on the user's original prompt, then briefly explain the solution. Do not lead with an implementation inventory:
BAD
❌ Removed implicit workspace carry-over from every "new thread" entry point (cmd+n / cmd+shift+o, sidebar v1/v2 buttons, command palette). New threads inherit only the project from context; branch, worktree, and env mode always come from the configured defaults. Deleted buildContextualThreadOptions, startNewThreadInProjectFromContext, and the v1 sidebar's seed-context machinery.
GOOD
✅ My "new worktree" default was ignored when starting new threads on existing worktrees. Super unintuitive. Now your preferences always apply.
End the description with the public model name and harness that made the changes, for example Created with <model> in <harness>. Include subagent models that wrote part of the change. Use the model name the harness reports. If model identity is unavailable, name the harness without guessing a model.
Before submission, check the title, description, quotes, and attachments for secrets and private details.
Open a real PR rather than a draft so review bots run. If gh pr create fails because the GraphQL rate limit is used up, open it through REST with gh api repos/<owner>/<repo>/pulls -f title=... -f head=... -f base=... -F body=@<file>. If the user also asked to babysit it, continue with the babysit-pr skill.
Do not post a follow-up PR comment unless it serves the user's request. When a comment is needed, use the leaving-pr-comments skill.
