github-issues
manage the lifecycle of GitHub Issues, including creation, triage, milestones, search, and sub-issue hierarchy
Découvrez les skills tools git workflows, comparez leurs dépôts et consultez leurs instructions.
manage the lifecycle of GitHub Issues, including creation, triage, milestones, search, and sub-issue hierarchy
foundational definitions for GitHub skills, safety rules, tool escalation, and security boundaries
manage branches and full pull request lifecycle, from creation to merge
Validate pull request source/target rules and draft standardised PR titles and Markdown descriptions that match repository GitHub Actions enforcement.
Maintain testing and formatting discipline aligned with the repository CI pipeline without automatically running tools.
GitHub Actions 워크플로우 로그를 조회하고 분석합니다. "CI 로그 확인해줘", "워크플로우 실패 원인 분석해줘", "GitHub Actions 상태 알려줘", "빌드 로그 보여줘", "테스트 실패 로그 확인" 등을 요청할 때 활성화됩니다.
요구사항 명세를 기반으로 프로젝트 아키텍처와 GitHub Actions CI 파이프라인을 설계합니다. "프로젝트 시작", "프로젝트 초기화", "CI 설정", "아키텍처 설계" 등의 요청 시 활성화됩니다.
요구사항 명세를 기반으로 프로젝트 구조와 CI 파이프라인을 설정합니다. "프로젝트 초기화해줘", "프로젝트 부트스트랩", "CI 설정해줘", "프로젝트 구조 만들어줘" 등을 요청할 때 활성화됩니다.
Generate descriptive commit messages by analyzing git diffs. Use when the user asks for help writing commit messages or reviewing staged changes.
Self-improvement workflow after fixing any bug. Analyzes root causes and updates project guidance (CLAUDE.md, skills, commands) to prevent similar bugs. MUST be invoked after completing any bug fix before marki...
Pre-commit validation checklist before staging and committing code. Use BEFORE every git commit to ensure code quality, tests pass, and documentation is updated. Triggers on "commit", "stage changes", "ready to...
Follow these patterns when implementing governance operations (copy, branch, transfer, promote, merge) in OptAIC. Covers artifact handling, RBAC mutations, lineage tracking, and activity emission.
This skill should be used when the user asks about "code review best practices", "how to review code", "review methodology", "code review framework", "impact prioritization", "root cause analysis", or needs gui...
Search GitHub issues, pull requests, and discussions across any repository. Activates when researching external dependencies (whisper.cpp, NAudio), looking for similar bugs, or finding implementation examples.
Manage and guide Hikaze-Model-Manager-2 Codex project work via the .codex governance system. Use when the user says "root skill" or asks to start development based on the root skill, or when asked to set up or...
Analyze changes, determine semantic version bump, build executables, and cut a GitHub release with Claude-written minimalist notes.
Comprehensive pre-production repository audit for preparing repos for public release. Use when the user wants to perform a "final sweep", "production check", "pre-release audit", or prepare a repository to be m...
課題作成時のGitブランチ・コミット・プッシュの標準手順を提供します。 ブランチ作成、コミットメッセージ作成、プルリクエスト作成時に自動参照されます。 「ブランチを作成」「コミット」「プッシュ」などのキーワードで自...
Tools to maintain the repository map. Use ONLY when the project structure has changed significantly.
Generate GitHub issues from an approved engineering specification. Use to break down a spec into implementable, atomic tasks with dependencies, sizing, and labels.
Generate GitHub issues from an approved engineering specification. Use to break down a spec into implementable, atomic tasks with dependencies, sizing, and labels.
Generate GitHub issues from an approved engineering specification. Use to break down a spec into implementable, atomic tasks with dependencies, sizing, and labels.
Validate generated GitHub issues for completeness and implementability. Reviews each issue for clear scope, actionable acceptance criteria, and sufficient context for implementation.
Inspect GitHub PR checks with gh, pull failing GitHub Actions logs, summarize failure context, then create a fix plan and implement after user approval. Use when a user asks to debug or fix failing PR CI/CD che...
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.