Gpt
Use GPT for long-running coding tasks: large refactors, feature implementation etc.From its SKILL.md
npx -y skills add metrovoc/cc-skill-opencode --skill gptAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.3 KB, 338 tokens by cl100k_base, as published. Nobody here has run it
GPT (via ocw)
Long-context coding. Best for: large refactors, feature implementation.
Prompt Guidelines
GPT strictly follows instructions. Provide as much high-level design context as possible:
- Architecture decisions, data flow, component responsibilities
- Constraints, edge cases, expected behaviors
Avoid:
- Contradictory requirements (GPT will struggle to reconcile conflicts)
- Code snippets — GPT writes code well on its own; use tokens for design info instead
Create Session (with worktree for code edits)
ocw new gpt --worktree
Returns:
- Line 1: 6-char hash
- Line 2: worktree path (e.g.,
/path/to/ocw-abc123)
The worktree is an isolated git branch. Work there freely.
Create Session (read-only, no worktree)
ocw new gpt
Chat
ocw chat <hash> << 'EOF'
your prompt
EOF
Chat with File
ocw chat <hash> -f /path/to/spec.md << 'EOF'
implement based on this
EOF
Worktree Workflow
ocw new gpt --worktree→ get hash + path- Work in worktree:
cd /path/to/ocw-{hash} - Edit, commit, push as needed
- When done:
git worktree remove /path/to/ocw-{hash}
List Sessions
ocw list
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.