Loading...
Loading...
Found 102 Skills
This skill should be used when a QA engineer wants to test or verify a completed task, run through acceptance criteria, check Gherkin scenarios against the implementation, record pass/fail results, or sign off on a ticket before merge. Triggers on phrases like "verify task
Shepherd a GitHub pull request all the way to merge-ready by relentlessly polling status and only acting once all automatic reviewers have finished. NEVER merges without explicit human approval. Use when the user says things like "shepherd this PR", "babysit this PR", "get this PR merge-ready", "wait for Cubic", "wait for Bugbot", or asks to drive a PR through review.
Runs the jackin' pre-merge gate, retires the roadmap item into docs, and squash-merges a pull request. Use when the operator runs /jackin-dev:merge-pr.
Create Pull Requests following best conventions. Use when opening PRs, writing PR descriptions, or preparing changes for review.
Create a pull request following project conventions
Commit, push, and open a PR with an adaptive, value-first description. Use when the user says "commit and PR", "push and open a PR", "ship this", "create a PR", "open a pull request", "commit push PR", or wants to go from working changes to an open pull request in one step. Produces PR descriptions that scale in depth with the complexity of the change, avoiding cookie-cutter templates.
Commit unstaged changes, push changes, submit a pull request.
s-skills 설치 후 MCP 서버(Linear/Slack/Notion)와 GitHub CLI를 대화형으로 설정하는 스킬. 사용 중인 도구만 골라 설정하고, 이미 돼 있으면 스킵, 안 돼 있으면 단계별 안내·검증까지 전부 끌고 간다. Use when asked "셋업", "setup", "처음 설정", "s-skills 설치했어요", or after installing s-skills.
Run a comprehensive pull request review using multiple specialized agents. Each agent focuses on a different aspect of code quality, such as comments, tests, error handling, type design, and general code review. The skill aggregates results and provides a clear action plan for improvements. Triggers include "review PR", "analyze pull request", "code review", and "PR quality check".
Use after creating PR - monitor CI pipeline, resolve failures cyclically until green or issue is identified as unresolvable
Git workflow standards, commit conventions, hooks, and pull request practices. Use this when users need guidance on Conventional Commits, Git hooks with Lefthook, pull request templates, .gitignore configuration, or Git workflow best practices for team collaboration.
Creates a Pull Request from current changes for OneKey app-monorepo. Use when user wants to create PR, submit changes, or merge feature branch. Handles branch creation, commit, push, and PR creation workflow.