Loading...
Loading...
Found 125 Skills
Lead Software Engineer. Use this skill whenever the user mentions coding, debugging, refactoring, or implementation, even if they don't explicitly ask for an "engineer." Use it to translate technical blueprints into clean code.
Check the latest test-related CI results for the current pull request.
Use when writing, generating, or drafting a pull request description. Always use this skill when the user asks to "write a PR description", "create a PR", "draft a pull request", "generate PR text", or similar. Produces a complete, structured PR description following the team's conventions: ticket-key title, Purpose, Approach with implementation details, and a Pre-Review Checklist.
Use when reviewing code, pull requests, branches, diffs, or changed files for quality, correctness, security, performance, and style issues.
Create GitHub Pull Request from specification using pull_request_template.md. Use when: spec needs to be converted to PR, spec is ready for review/merge, need to automate PR creation from specification file with template-based body and title.
Git workflow guidance for commits, branches, and pull requests
You are a GitHub issue resolution expert specializing in systematic bug investigation, feature implementation, and collaborative development workflows. Your expertise spans issue triage, root cause an
Reviews code changes for correctness, maintainability, security, and adherence to project conventions. Use when reviewing PRs, auditing recent changes, or getting a second opinion on implementation quality.
Analyze failed GitHub Action jobs for a pull request.
Perform security-focused review of code diffs and pull requests, identifying newly introduced vulnerabilities, security regressions, and unsafe patterns in changed code.
Git 설정부터 PR 생성까지 전 과정을 자동으로 실행합니다. "자동으로 해줘", "전부 자동화", "원클릭 PR", "자동 설정" 같은 요청에 사용됩니다.
GitHub operations via `gh` CLI: issues, PRs, CI runs, code review, API queries. Use when: (1) checking PR status or CI, (2) creating/commenting on issues, (3) listing/filtering PRs or issues, (4) viewing run logs. NOT for: complex web UI interactions requiring manual browser flows (use browser tooling when available), bulk operations across many repos (script with gh api), or when gh auth is not configured.