메뉴
Load when the user asks to create a GitHub issue or PR, push code, commit changes, or do anything that touches a git repository on GitHub.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Load when the user asks to queue, enqueue, or add a coding task to the fleet, dispatch a job to a repo, or ask the fleet worker to fix something. Trigger phrases: "add to fleet", "queue a job for", "send to fleet", "dispatch to".
Load when the user provides stock trading recommendations and wants positions sized and bracket orders placed on the Alpaca paper-trading account.
Load when the user wants to navigate a website, click through a flow, fill a form, extract data from a page, or record an interaction as a reusable playbook.
Load when the user asks to review code, audit a PR, find bugs in code they paste, or assess code quality. Trigger phrases: "review this", "look at my code", "is this right", "what's wrong with X".
Load when the user is responding to a customer inquiry, complaint, or support ticket and needs help drafting a reply with the right tone.
Load when the user wants analysis on a dataset — trends, distributions, summary statistics, or insights from a CSV/JSON/Excel file.
| name | GitHub Operations |
| slug | github-operations |
| description | Load when the user asks to create a GitHub issue or PR, push code, commit changes, or do anything that touches a git repository on GitHub. |
| icon | Github |
| color | #1f2937 |
| version | 1.1.0 |
| category | coding |
| tools | ["create_github_issue","create_github_pr","commit_and_push","read_file"] |
| config_schema | {"type":"object","properties":{"default_repo":{"type":"string","default":""},"branch_prefix":{"type":"string","default":"feature/"}}} |
Default repo: {default_repo}. Branch prefix: {branch_prefix}.
Issues — title is an imperative verb + concise description ("Fix auth timeout on mobile"). Body: Problem → Repro → Expected vs Actual → Environment → Proposed Fix.
PRs — branch {branch_prefix}kebab-case-description. Body: Summary → Test plan → Screenshots if UI → Breaking changes. Link the issue with Closes #N.
Commits — type(scope): description. Types: feat, fix, refactor, docs, test, chore.
Never force-push to main or master. Never skip hooks (--no-verify) unless the user explicitly asks.
