create-pr
Creates pull requests with bilingual documentation updates. Use when user asks to create PR, make a pull request, or submit changes for review. Automatically updates both English and Chinese README files.
Discover tools git workflows skills, compare source repositories and read the instructions for each workflow.
Creates pull requests with bilingual documentation updates. Use when user asks to create PR, make a pull request, or submit changes for review. Automatically updates both English and Chinese README files.
Helps write Git commit messages following the Conventional Commits specification. Use this skill when the user asks to commit changes, write commit messages, format commits, or mentions git commits.
Use this skill when asked to create a pull request (PR). It ensures all PRs follow the repository's established templates and standards.
Create, evaluate, and optimize GitHub Actions workflows and custom actions. Use when building CI/CD pipelines, creating workflow files, developing custom actions, troubleshooting workflow failures, performing s...
変更内容を確認し、論理的な単位で複数のコミットに分けて実行します
GitHub issue state machine and code integration patterns. Covers state transitions (needs-triage → accepted → in-progress → completed), branch naming (feat/123-desc), PR linking (Closes
Standardized GitHub issue templates for bugs, features, and tasks. Provides title formats, body structure, and required sections. Use when creating issues to ensure consistency. Includes copy-paste templates in...
Git worktree patterns, best practices, templates, and quick reference. Use when user asks about "worktree best practices", "worktree patterns", "git worktree help", "worktree template", "worktree mode semantics...
Label taxonomy and triage workflow for GitHub issues. Defines type labels (bug/feature/enhancement/docs/chore), priority levels (critical/high/medium/low), status labels, and triage decision workflow. Use when...
Use when the user needs technical research, architecture validation, documentation generation, or code review. Default is read-only mode, but can enable auto-approve (-y) for code changes.
Design automation workflows and pipelines. Use when creating CI/CD, task automation, or process flows.
Initialize new projects with best practices. Use when starting new codebases or setting up repos.
Automatically triggered for code reviews, PR analysis, and quality checks. Use when reviewing changes, checking code quality, or preparing commits.
Create a commit following Vantle's release message standards. Analyzes staged changes and generates a structured commit message with component sections linking to Readme.md files. Use /commit when ready to comm...
Store and manage coding context in git. Use when saving decisions, tracking tasks, planning complex work, or coordinating with other agents. Activates on mentions of "save context", "track task", "planning", or...
Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit mes...
Generate nested AGENTS.md coding guidelines per module (monorepo-aware), detect languages/tooling, ask architecture preferences, and set up missing formatters/linters (Spotless for JVM).
Create or update root and nested AGENTS.md files that document scoped conventions, monorepo module maps, cross-domain workflows, and (optionally) per-module feature maps (feature -> paths, entrypoints, tests, d...
Create a high-quality pull request: branch, focused changes, lint/build, conventional commit, and a clear PR description with validation steps.
Audits local HyperFleet repositories against team architecture standards dynamically fetched from the architecture repo. Activates when users ask to audit repos, check standards compliance, or identify standard...
Go modules and dependency management
GitHub Actions, GitLab CI, Jenkins, and automated deployment pipelines
Git workflows, branching strategies, collaboration, and code management
Best practices for writing clear, effective pull request descriptions. Use when creating PRs to ensure they communicate changes effectively to reviewers.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.