code-review
Review code changes for quality, security, performance, and maintainability. Use when reviewing PRs, diffs, or code files. Provides structured feedback with severity levels.
Discover content media git workflows skills, compare source repositories and read the instructions for each workflow.
Review code changes for quality, security, performance, and maintainability. Use when reviewing PRs, diffs, or code files. Provides structured feedback with severity levels.
Create well-formatted git commits using Conventional Commits format. Use when committing changes, reviewing commit messages, or splitting changes into atomic commits.
GitHub ISSUEを作成します。ユーザーがISSUEの作成を依頼したときに使用します。
変更を適切な粒度に分割してコミットします。コード変更完了時に自動的に提案します。
現在のブランチ名からGitHub ISSUEの情報を取得し、PRを作成します。コミット完了後に自動的に提案します。
Git commit workflow with conventional commits and staging hygiene. Use when asked to stage changes, write commit messages, or manage commits in multi-worktree setups.
Git workflows for feature branches, merges, and PR creation with GitHub CLI. Use when asked to manage branches, sync with base, resolve conflicts, or create PRs.
Iterative spec-driven development workflow using subagents. Use when user wants to build a feature from scratch, needs help writing a detailed spec, or asks for implementation with verification. Triggers on phr...
Pick up and implement the next available feature from /.agent-features/. Use when user says "develop feature", "work on next feature", "implement feature", or starts a new session to continue feature-driven dev...
Initialize a project with a CLAUDE.md file by exploring the codebase and auto-detecting development workflows. Use when user wants to set up Claude Code for a new project, create a CLAUDE.md, or run /init-proje...
Generate English commit message with emoji prefix and push. Use when user wants to commit and push changes, or uses /commit.
Deploy Codex or Gemini as working agents to implement tasks. Use when you want another AI to actually write code, not just review. (project)
現在のブランチでPull Requestを作成し、CIステータスを確認。「/issue-pr」で使用
GitHub Issueの作業を開始する。ブランチを作成してチェックアウト。「/issue-start 4」のように使用
Provides comprehensive knowledge about moonrepo/moon for monorepo management and task running. Use when user asks about moon configuration, workspace setup, task definitions, CI/CD integration, proto toolchain,...
Create a pull request from current changes with interactive file selection, pre-commit validation, testing, and automated PR creation. Use when the user asks to "create a PR", "make a pull request", "open a PR"...
Automate CI/CD pipelines with GitHub Actions. Master workflow syntax, event triggers, jobs, steps, environment variables, secrets, artifacts, matrix builds, and deployment patterns. Use when setting up automate...
Analyze a repository to generate recommended Claude Code settings.json permissions. Use when setting up a new project, auditing existing settings, or determining which read-only bash commands to allow. Detects...
Create pull requests following best practices. Use when opening PRs, writing PR descriptions, or preparing changes for review. Follows conventional commit and PR conventions.
Create commit messages following conventional commit conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with issue references.
Comprehensive workflow for implementing new features or complex changes. Use when the user asks for a new component, page, or significant refactor.
MANDATORY for all git operations. Enforces git commit message conventions. STRICTLY REQUIRED when user asks to commit changes or generate commit messages. DO NOT manually run git commands, always delegate to th...
End-to-end GitHub issue fix workflow using gh CLI, local code changes, builds/tests, and git push. Use when asked to take an issue number, implement a fix, run builds/tests, commit with a closing message, and p...
Create user-facing App Store release notes from git history. Use when asked to generate release changelog, App Store "What's New" text, or release notes based on git tags.
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.