scriptoriumadmin/GitNexus
1
0
Fork 0
mirror of https://github.com/abhigyanpatwari/GitNexus.git synced 2026-10-10 03:27:59 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 3

docs(skills): document Codex user-level install path for gitnexus-plan

Browse source 
Codex discovers SKILL.md skills from ~/.agents/skills (same path the other
gitnexus-* skills install to); README now documents the cp install plus the
optional ~/.codex/prompts slash-command file, with the prompt body preferring
the repo copy and falling back to the user-level install.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Gergo Magyar 2026-07-11 07:37:20 +00:00
parent 884a6aeb2c
commit 68b05986e0
1 changed files with 18 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

24
.claude/skills/gitnexus-plan/README.md
View file

@ -22,19 +22,31 @@ Output: `docs/plans/YYYY-MM-DD-gitnexus-plan-<slug>.md` — a 13-section plan wh
section 11 is a machine-readable **implementation context pack** that a
follow-up agent can consume without re-investigating the repository.
### Codex (optional user-level slash command)
### Codex (user-level install)
Codex prompts are user-level only (not repo-shareable). To get a
`/gitnexus-plan` slash command, create `~/.codex/prompts/gitnexus-plan.md`:
Codex discovers SKILL.md skills from `~/.agents/skills/` (the same path the
other `gitnexus-*` skills install to). To make this skill auto-discoverable in
every Codex session:
```
cp -r .claude/skills/gitnexus-plan ~/.agents/skills/gitnexus-plan
```
Codex prompts are user-level only (not repo-shareable). Optionally, for an
explicit `/gitnexus-plan` slash command, also create
`~/.codex/prompts/gitnexus-plan.md`:
```markdown
---
description: Implementation-ready engineering plan via GitNexus + PDG + source verification
argument-hint: <task description>
---
Read `.claude/skills/gitnexus-plan/SKILL.md` in this repo and follow it for: $ARGUMENTS
Load its references/ files at the phases that call for them. Planning only — never
edit code; the only repo file you write is the plan document.
Use the gitnexus-plan skill for: $ARGUMENTS
Read `~/.agents/skills/gitnexus-plan/SKILL.md` (if this repo has its own copy at
`.claude/skills/gitnexus-plan/SKILL.md`, prefer that one) and follow its phases in
order, loading its `references/` files at the phases that call for them. Planning
only — never edit code; the only repo file you write is the plan document.
```
## Architecture note: how GitNexus and the agent interact