Loading...
Loading...
Found 118 Skills
Generate and manage changelogs from git history. Use for release notes, tracking breaking changes, and maintaining project history.
Use when reviewing pull requests with comprehensive code analysis, incremental or full review options, and constructive feedback - provides thorough code reviews with severity ratings
PR stacking workflow for breaking large features into smaller, dependent PRs. Use when planning multi-step features, creating dependent branches, or rebasing stacked changes.
Amp Team Usage
Create GitHub Issue from spec documents — Auto-generate structured Feature Issues from specifications. Analyzes spec documents (requirement.md, design.md, tasks.md) in .specs/{feature}/ and generates a structured Feature Issue via gh issue create. Best used with specs created by spec-generator. English triggers: - "Create issue from spec", "Register spec as issue" - "Convert spec to GitHub issue", "Publish spec to issue" - After spec-generator: "Turn this into an issue" 日本語トリガー: - 「仕様書をIssueにして」「Issueに登録して」「specからIssue作成」 - 「仕様書からIssue生成」「specをIssueに変換」 - spec-generator完了後に「これをIssueにして」「Issueにして」
Git과 GitHub 초기 설정을 단계별로 진행합니다. "git 설정", "처음 시작", "GitHub 로그인", "깃 세팅" 같은 요청에 사용됩니다.
Git 설정부터 PR까지의 전체 진행 상황을 체크리스트로 보여주고 현재 단계를 안내합니다. "어디까지 했지?", "진행 상황", "다음 단계" 같은 질문에 사용됩니다.
Git 설정부터 PR 생성까지 전 과정을 자동으로 실행합니다. "자동으로 해줘", "전부 자동화", "원클릭 PR", "자동 설정" 같은 요청에 사용됩니다.
Set up GitHub CLI and Vercel CLI, authenticate both, create a repo, and link it to Vercel for automatic deployments. One-time setup that makes all other Treehaus builder skills work.
Configure GitHub authentication for Cyrus — gh CLI login and git config for creating pull requests.
Automatically create a PR to register insights, conventions, and best practices obtained from the current project as rules in the TBSten/skills repository. It runs the entire end-to-end process: collecting insights from the project's CLAUDE.md, .claude/rules/ directory and codebase, packaging them as reusable Claude Code rules, and creating the PR. Rules are files stored in .claude/rules/, and unlike skills, they do not require frontmatter. RULE.md serves as the main rule body, while detailed documentation (<rule-name>.md / <rule-name>.ja.md) is placed directly under the rules/ directory. Use when the user requests: "Register insights as rules", "contribute rule", "Share this rule", "Register as a rule", "Compile rules into a PR", "Turn this convention into a rule", "Turn best practices into rules". gh CLI and git must be installed.
Create GitHub pull requests from the current branch with auto-generated titles, descriptions, reviewers, and labels. Use this skill whenever the user wants to create a PR, open a pull request, submit code for review, push changes for merge, or mentions "PR", "pull request", "code review", or "merge request". Also trigger when the user says things like "I'm done with this feature", "ready to submit", "open a draft PR", or "send this for review". Works with GitHub CLI by default, with guidance for GitLab and Bitbucket.