gpt
- Repo stars 330
- License MIT
- Author repo claude-skill-registry
- Domain
- Data
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 94 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @majiayu000 · MIT
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No explicit requirements detected
- Detected file/system behavior
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
# GPT-5.2 (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)
```bash
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)
```bash
ocw new gpt
```
## Chat
```bash
ocw chat <hash> << 'EOF'
your prompt
EOF
```
## Chat with File
```bash
ocw chat <hash> -f /path/to/spec.md << 'EOF'
implement based on this
EOF
```
## Worktree Workflow
1. `ocw new gpt --worktree` → get hash + path
2. Work in worktree: `cd /path/to/ocw-{hash}`
3. Edit, commit, push as needed
4. When done: `git worktree remove /path/to/ocw-{hash}`
## List Sessions
```bash
ocw list
```
Sections and files
Listed in source order.
sections -> Prompt Guidelines → Create Session (with worktree for code edits) → Create Session (read-only, no worktree) → Chat → Chat with File → Worktree Workflow
terms -> high-level design context · Avoid · Long-context coding. · GPT strictly follows instructions. · The worktree is an isolated git branch. · 1. ocw new gpt --worktree → get hash + path 2.
files/cmd -> /path/to/ocw-abc123 · ocw new gpt --worktree · cd /path/to/ocw-{hash} · git worktree remove /path/to/ocw-{hash}
body sha256 -> 062e139dcc67
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)
Create Session (with worktree for code edits)
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.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}