Loading...
Loading...
Found 137 Skills
Use when checking live Capy task or PR state through Brave, Computer Use, or a Capy browser panel.
Specialized agent for multi-repository analysis, searching remote codebases, retrieving official documentation, and finding implementation examples using GitHub CLI, Context7, and Web Search. Use proactively when unfamiliar libraries or frameworks are involved, working with external dependencies, or needing examples from open-source projects to understand best practices and real-world implementations.
Manage GitHub via GitHub CLI (gh): repos, issues, pull requests, Actions, releases, secrets/variables, projects, gists, searches, and API access. Auto-activates on: "gh", "github cli", "github issue", "github pr", "pull request", "github actions", "workflow", "run", "github release", "release", "gh api", "github repo", "github secret", "github variable", "ci status", "monitor ci", "check ci", "watch ci", "pr dashboard", "pr overview", "open prs", "my prs", "pr status".
Use after completing implementation - create pull request with complete documentation, proper labels, linked issues, and verification summary
Systematic workflow for addressing PR review comments using gh-pr-review CLI. Use when the user wants to work through PR review comments and prefers the gh-pr-review tool over helper scripts.
Git version control and GitHub CLI workflows for commits, branches, pull requests, and code reviews with professional commit message practices.
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にして」
Creates a Pull Request from current changes for OneKey app-monorepo. Use when user wants to create PR, submit changes, or merge feature branch. Handles branch creation, commit, push, and PR creation workflow.
Reference for GitHub CLI (gh) - READ-ONLY operations only
Publish a workflow learning to the groovebook shared commons as a GitHub PR. Use after groove-work-compound when a learning is worth sharing.
Push current branch changes to origin and create or update the corresponding pull request; use when asked to push, publish updates, or create pull request.