pre-work-research
Use before starting implementation - research repository documentation, codebase patterns, and external resources to inform the approach
Use before starting implementation - research repository documentation, codebase patterns, and external resources to inform the approach
GitHub Pull RequestのレビューコメントにClaude Code風に効率的に対応するスキル。レビュー内容の確認、各コメントへの返信作成、スレッドのresolve処理を一貫したワークフローで実行。PRレビュー対応、レビューコメント返信、レビュー指摘への対応時に使用。
Parse GitHub AI analysis comment sections for architectural alignment, technical feasibility, implementation suggestions, and testing strategy
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.
Inspect Terraform module specs from cache when seeing module sources.
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.
Use when a review finding cannot be fixed in current PR - creates properly documented tracking issue with full context, linked to parent, following full issue-driven-development process
Enforce semantic commit practices with proper file staging and prefix usage. Use when committing code, managing git history, or when user mentions git/commit/コミット.
Install and manage dotfiles in this repository. Use when adding a new config file to be tracked, symlinking a dotfile, or modifying which files are managed by the dotfiles repo.
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
Implementation workflow for SpecFlux projects. Enforces test-first development, one commit per task, and API status updates. This skill is always active when writing code in SpecFlux projects.
This skill should be used when the user works with Jujutsu (jj) version control, asks to "commit with jj", "rebase in jj", "use revsets", "create bookmarks", "push to git with jj", "split commits", "squash changes", "edit history", or mentions jj-specific concepts like changes, revsets, bookmarks, operation log, or anonymous branches.
Comprehensive guide for using GitHub CLI (gh) to interact with GitHub from the command line. Use when (1) Managing GitHub repositories, issues, pull requests, or releases from terminal, (2) Automating GitHub workflows in scripts, (3) Creating or managing pull requests, (4) Working with GitHub issues, (5) Creating releases or managing repository operations, (6) Integrating GitHub operations into development workflows, (7) Using GitHub CLI commands in automation scripts
Create GitHub pull requests with proper issue linking, comprehensive descriptions, and quality metrics for WescoBar project