From 0c5b481cc488c34f1303ea01c7b56204997a80ab Mon Sep 17 00:00:00 2001 From: Liam Rohan Date: Sun, 22 Mar 2026 09:48:45 +0000 Subject: [PATCH] replace use of gh cli with fj cli --- improve-codebase-architecture/SKILL.md | 4 ++-- prd-to-issues/SKILL.md | 8 ++++---- triage-issue/SKILL.md | 4 ++-- 3 files changed, 8 insertions(+), 8 deletions(-) diff --git a/improve-codebase-architecture/SKILL.md b/improve-codebase-architecture/SKILL.md index 87d858b..6d0da5e 100644 --- a/improve-codebase-architecture/SKILL.md +++ b/improve-codebase-architecture/SKILL.md @@ -71,6 +71,6 @@ After comparing, give your own recommendation: which design you think is stronge ### 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. diff --git a/prd-to-issues/SKILL.md b/prd-to-issues/SKILL.md index 893a56f..3c935bb 100644 --- a/prd-to-issues/SKILL.md +++ b/prd-to-issues/SKILL.md @@ -11,9 +11,9 @@ Break a PRD into independently-grabbable GitHub issues using vertical slices (tr ### 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 ` (with comments). +If the PRD is not already in your context window, fetch it with `fj issue view ` (with comments). ### 2. Explore the codebase (optional) @@ -49,9 +49,9 @@ Ask the user: 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. diff --git a/triage-issue/SKILL.md b/triage-issue/SKILL.md index 2b5b9fc..9c76b73 100644 --- a/triage-issue/SKILL.md +++ b/triage-issue/SKILL.md @@ -54,9 +54,9 @@ Rules: - 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. -### 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.