ldr/skills
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

replace use of gh cli with fj cli

Browse source
This commit is contained in:
Liam Rohan 2026-03-22 09:48:45 +00:00
parent bca0ac3e4d
commit 0c5b481cc4
3 changed files with 8 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
improve-codebase-architecture/SKILL.md
View file

@ -71,6 +71,6 @@ After comparing, give your own recommendation: which design you think is stronge
### 6. User picks an interface (or accepts recommendation) ### 6. User picks an interface (or accepts recommendation)
### 7. Create GitHub issue ### 7. Create issue
Create a refactor RFC as a GitHub issue using `gh issue create`. Use the template in [REFERENCE.md](REFERENCE.md). Do NOT ask the user to review before creating — just create it and share the URL. Create a refactor RFC as an issue using `fj issue create`. Use the template in [REFERENCE.md](REFERENCE.md). Do NOT ask the user to review before creating — just create it and share the URL.

8
prd-to-issues/SKILL.md
View file

@ -11,9 +11,9 @@ Break a PRD into independently-grabbable GitHub issues using vertical slices (tr
### 1. Locate the PRD ### 1. Locate the PRD
Ask the user for the PRD GitHub issue number (or URL). Ask the user for the PRD issue number (or URL).
If the PRD is not already in your context window, fetch it with `gh issue view <number>` (with comments). If the PRD is not already in your context window, fetch it with `fj issue view <number>` (with comments).
### 2. Explore the codebase (optional) ### 2. Explore the codebase (optional)
@ -49,9 +49,9 @@ Ask the user:
Iterate until the user approves the breakdown. Iterate until the user approves the breakdown.
### 5. Create the GitHub issues ### 5. Create the issues
For each approved slice, create a GitHub issue using `gh issue create`. Use the issue body template below. For each approved slice, create an issue using `fj issue create`. Use the issue body template below.
Create issues in dependency order (blockers first) so you can reference real issue numbers in the "Blocked by" field. Create issues in dependency order (blockers first) so you can reference real issue numbers in the "Blocked by" field.

4
triage-issue/SKILL.md
View file

@ -54,9 +54,9 @@ Rules:
- Include a final refactor step if needed - Include a final refactor step if needed
- **Durability**: Only suggest fixes that would survive radical codebase changes. Describe behaviors and contracts, not internal structure. Tests assert on observable outcomes (API responses, UI state, user-visible effects), not internal state. A good suggestion reads like a spec; a bad one reads like a diff. - **Durability**: Only suggest fixes that would survive radical codebase changes. Describe behaviors and contracts, not internal structure. Tests assert on observable outcomes (API responses, UI state, user-visible effects), not internal state. A good suggestion reads like a spec; a bad one reads like a diff.
### 5. Create the GitHub issue ### 5. Create the issue
Create a GitHub issue using `gh issue create` with the template below. Do NOT ask the user to review before creating - just create it and share the URL. Create an issue using `fj issue create` with the template below. Do NOT ask the user to review before creating - just create it and share the URL.
<issue-template> <issue-template>