메뉴
Use the scope CLI for developer-first issue tracking in this repo. Trigger when the user asks to create/update/list/show issues, manage comments, conflicts, indexes, project mapping, or scope config files, or when demonstrating or scripting the scope CLI.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
The basics of how to program GPUs using Mojo. Use this skill in addition to mojo-syntax when writing Mojo code that targets GPUs or other accelerators. Use targeting code to NVIDIA, AMD, Apple silicon GPUs, or others. Use this skill to overcome misconceptions about how Mojo GPU code is written.
Aids in writing Mojo code that interoperates with Python using current syntax and conventions. Use this skill in addition to mojo-syntax when writing Mojo code that interacts with Python, calls Python libraries from Mojo, or exposes Mojo types/functions to Python. Also use when the user wants to build Python extension modules in Mojo, wrap Mojo structs for Python consumption, or convert between Python and Mojo types.
Help to write Mojo code using current syntax and conventions. Always use this skill when writing any Mojo code, including when other Mojo-specific skills (e.g., mojo-gpu-fundamentals) also apply. Use when writing Mojo code, translating projects to Mojo, or otherwise generating Mojo. Use this skill to overcome misconceptions with how Mojo is written.
| name | scope-cli |
| description | Use the scope CLI for developer-first issue tracking in this repo. Trigger when the user asks to create/update/list/show issues, manage comments, conflicts, indexes, project mapping, or scope config files, or when demonstrating or scripting the scope CLI. |
Use the scope CLI in this repo to manage local-first issues stored as markdown snapshots plus JSONL event logs. Prefer CLI commands over manual file edits.
scope issues init --project <name>scope issues create --project <name> --title "..." [--priority p1] [--assignee ...] [--label ...] [--body "..."] [--body-file ./issue.md]scope issues list --project <name>scope issues show --project <name> <id>scope issues update <id> --status in_progress --add-label planningscope issues close <id> / scope issues reopen <id>scope issues delete <id> / scope issues restore <id> (--force is permanent)scope issues edit <id>
/dev/stdin, <<EOF) in agent shells; prefer --body, a real file path, or scope issues editscope issues comments add <id> --body "..." or --body-file ...scope issues comments list <id> [--json]scope issues index status|rebuild|verifyscope issues rebuild to regenerate snapshots + index from eventsscope issues projects [--json]scope issues project show --project <name>scope issues project link --project <name> --path /path/to/reposcope issues project links --project <name> [--json]scope issues conflicts listscope issues conflicts show <id>scope issues conflicts resolve <id> --keep local|remoteRead these when you need the detailed spec or schema:
references/cli.md for command surface and file layoutreferences/specs.md for links to the full design docs in docs/