Loading...
Loading...
Found 52 Skills
Plan a new feature from concept to approved implementation plan. Activates Product Council for strategic evaluation, then Feature Council for technical planning. Produces a documented decision and scoped task breakdown. Use when starting any new feature work.
Coordinate PR mining to extract tribal knowledge and coding standards from GitHub PR history. Use when mining review comments, extracting coding rules, tracking mining jobs, or analyzing reviewer patterns across repositories. Use for "mine PRs", "extract standards", "coding rules from reviews", or "reviewer patterns". Do NOT use for code review, linting, static analysis, or writing new coding standards from scratch without PR data.
GitHub PR review threads—KEEP/DISCARD triage, replies, KEEP-only code changes, lint/test/push. Open PRs only; not for creating PRs (create-pr-jp).
A skill for reviewing a specific diff and showing the findings as comments inside difit (the diff viewer). Use it to review branch diffs, commit diffs, or GitHub PRs, then preload findings or code explanations into difit with `--comment` before launching it for the user.
Verify that a pull request fully implements the requirements described in its linked GitHub issue. Use when asked to "verify PR implementation", "check PR coverage", "does PR implement the issue", "verify PR against issue", "is PR complete", or "PR completeness check". Extracts the linked issue from the PR body or GitHub linked issues, analyzes the diff against issue requirements, and reports either missing items or confirms 100% coverage.
Add before/after comparison screenshots to a PR using browser automation. Captures UI on the base branch and the PR branch, saves to docs/screenshot/, and updates the PR body with a side-by-side comparison table using GitHub CDN URLs.
Guidelines for git and GitHub operations in the WooCommerce repository.
Retrieve GitHub user profile and repository information using the gh CLI tool. Use when the user asks about their GitHub profile, statistics, repositories, or wants to view their GitHub information. Examples: Show me my GitHub profile, What are my top repositories, Get my GitHub stats.
This skill should be used when you need to create, open, or edit a pull request (PR), or the user asks to "create a PR", "open a PR", "submit a PR", "raise a PR", "file a PR", "make a PR", "create a pull request", "open a pull request", "new PR", or any variation requesting GitHub pull request creation.
When the user asks to fix, address, or work on PR review comments — fetch review comments from a GitHub pull request and apply fixes to the local codebase. Requires gh CLI.
Generate objective reference check reports about the user from real AI collaboration data — session history, git logs, GitHub profile, and memory files. Like a colleague writing a professional reference, but grounded in actual shared work. Use whenever the user asks to evaluate them as a developer, wants a reference letter, work style analysis, introduced by my agents content, interview prep from collaboration history, or blog topics from past discussions. Triggers on: write a reference, analyze my work patterns, what do you think of me, 나에 대한 레퍼런스 써줘, 내 작업 스타일 분석해줘. Not for general code review, architecture docs, cover letters, or codebase-only analysis.
Validate-then-fix workflow for PR review comments: Fetch, Validate, Plan, Fix, Commit. Use when user wants to address PR feedback, fix review comments, or resolve reviewer requests. Use for "fix PR comments", "address review", "pr-fix", or "resolve feedback". Do NOT use for creating PRs, reviewing code without fixing, or general debugging unrelated to PR comments.