issue-prerequisite
Use before starting ANY work - hard gate ensuring a GitHub issue exists, creating one if needed through user questioning
Find the perfect capability for your agent.
Use before starting ANY work - hard gate ensuring a GitHub issue exists, creating one if needed through user questioning
Analyzes git changes and creates commits with Korean messages following Conventional Commits. Use when the user asks to commit, make commits, organize changes, or says "커밋해줘", "변경사항 정리해줘", "커밋 만들어줘".
GitHub Pull RequestのレビューコメントにClaude Code風に効率的に対応するスキル。レビュー内容の確認、各コメントへの返信作成、スレッドのresolve処理を一貫したワークフローで実行。PRレビュー対応、レビューコメント返信、レビュー指摘への対応時に使用。
Parse GitHub AI analysis comment sections for architectural alignment, technical feasibility, implementation suggestions, and testing strategy
Generate comprehensive, reviewer-ready code review documents from git diffs. Use this when the user provides code changes (git diff output, file changes, or asks to review code changes) and wants a structured review document. Creates detailed analysis covering change overview, business flow, key code explanation, risk assessment, and review recommendations. Supports both manual diff input and automatic git workspace detection. Particularly useful for reviewing pull requests, feature branches, or any code changes requiring thorough documentation for reviewers.
MANDATORY before any GitHub project operations - caches project metadata to prevent rate limit exhaustion. Called by session-start. Other skills MUST use cached data.
Git troubleshooting techniques including recovering lost commits, fixing merge conflicts, resolving detached HEAD, and diagnosing repository issues. Use when user encounters git errors or needs to recover from mistakes.
Safely introduce external Git repositories as reference materials. Responsible for managing the `_reference` directory, ensuring external code is read-only and does not pollute the project's version control.
Create a GitHub pull request (PR) with proper formatting and content guidelines. Invoke this skill whenever the user wants to create, open, or submit a PR (or GitLab MR, Gerrit CR).
Check if pull request already exists for current branch to support workflow resumption and prevent duplicate PR creation
Create single atomic commit with proper message format, issue linking, and pre-commit hook validation for WescoBar workflows
Implement a feature or fix based on an issue. Use when given an issue URL to work on, or when implementing changes described in a tracked issue. Supports GitHub, Linear, and GitLab.
Enforce semantic commit practices with proper file staging and prefix usage. Use when committing code, managing git history, or when user mentions git/commit/コミット.
Create or update .gitignore files by fetching standard templates from the GitHub/gitignore repository.
Load conductor workflow state from previous session and determine resumption point by analyzing git state and saved JSON state file
Use throughout all work - ensures GitHub issues are updated continuously as work happens, not batched at the end