create-claude-rails 0.5.4 → 0.5.6

package/lib/cli.js

@@ -579,22 +579,7 @@ async function run() {
         entry.description = registry.projects[existingIdx].description || '';
         registry.projects[existingIdx] = entry;
       } else {
-        // New project — ask for name/description if interactive
-        if (!flags.yes && !flags.lean) {
-          const { projName } = await prompts({
-            type: 'text',
-            name: 'projName',
-            message: `Project name?`,
-            initial: entry.name,
-          });
-          if (projName) entry.name = projName;
-          const { projDesc } = await prompts({
-            type: 'text',
-            name: 'projDesc',
-            message: 'One line about what it is:',
-          });
-          if (projDesc) entry.description = projDesc;
-        }
+        // Register with folder name. /onboard fills in name and description later.
         registry.projects.push(entry);
       }
       fs.writeFileSync(registryPath, JSON.stringify(registry, null, 2) + '\n');

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-claude-rails",
-  "version": "0.5.4",
+  "version": "0.5.6",
   "description": "Claude on Rails — opinionated process scaffolding for Claude Code projects",
   "bin": {
     "create-claude-rails": "bin/create-claude-rails.js"

package/templates/skills/debrief/phases/upstream-feedback.md

@@ -88,17 +88,44 @@ points to a local path rather than a `node_modules` path):
 - Add frontmatter: `type: field-feedback`, `source: [project]`,
   `date: [ISO date]`, `component: [skill/phase name]`
 
-**If not linked** (CoR is installed from npm):
-
-- Open a GitHub issue on the CoR repo
-- Title: `Field feedback: [short title]`
-- Label: `field-feedback` (create if needed)
-- Body: the feedback markdown
-
-**If neither works** (no link, no gh access):
-
-- Output the feedback to the terminal and tell the user to file
-  it manually or copy it to the CoR repo
+**If not linked**, check whether `gh` is available and authenticated
+(`gh auth status` exits 0). Then present the user with their options:
+
+- **If `gh` works**, offer two choices:
+  > "I can send this as a GitHub issue so the developer sees it
+  > directly, or save it locally. Which do you prefer?"
+  >
+  > 1. Send as GitHub issue
+  > 2. Save locally (I'll send it later or pass it along myself)
+
+  If they choose GitHub:
+  - Open a GitHub issue on `orenmagid/claude-on-rails`
+  - Title: `Field feedback: [short title]`
+  - Label: `field-feedback` (create if needed)
+  - Body: the feedback markdown
+
+- **If `gh` is not available** (most common for non-developers):
+  > "I'll save this feedback locally for now. If you want, you can
+  > pass it along to the developer yourself, or set up a free GitHub
+  > account so future feedback goes directly to them. Here's a guide
+  > if you're interested:
+  > https://github.com/orenmagid/claude-on-rails/blob/main/GITHUB-SETUP.md
+  > — totally optional. Your feedback is saved either way."
+
+  Only show the GitHub setup suggestion the first time. Track whether
+  it's been shown by checking for a `cor-feedback-gh-prompted` key
+  in `.corrc.json`. After the first time, just say "Saved locally."
+
+**For either local save path:**
+
+- Append the feedback to `~/.claude/cor-feedback-outbox.json` as a
+  JSON array entry with fields: `source` (project name), `date`,
+  `component`, `title`, `body`, `status: "pending"`
+- Create the file if it doesn't exist (initialize with `[]`)
+
+**Flushing the outbox:** If a user later sets up `gh` and asks to
+send saved feedback, read the outbox, post each `pending` entry as
+a GitHub issue, and update its status to `"sent"` with the issue URL.
 
 ### 5. Done
 

package/templates/skills/onboard/phases/generate-context.md

@@ -69,6 +69,21 @@ Common re-run updates:
 - Updating work tracking configuration after switching tools
 - Removing stale information that no longer applies
 
+## Update Project Registry
+
+After generating the context layer, update `~/.claude/cor-registry.json`
+with what you learned from the interview. The installer registers the
+project with just its folder name and an empty description — onboard
+is where the real name and description get filled in.
+
+Find this project's entry by path and update:
+- **`name`** — the project's actual name (from the interview, not the
+  folder name, unless they match)
+- **`description`** — one line about what the project does
+
+This is a silent update — don't ask the user to confirm registry changes
+separately. The information already came from the interview.
+
 ## Quality Standards
 
 - **Populated, not padded.** Every section should contain real project

package/templates/skills/onboard/phases/interview.md

@@ -23,12 +23,15 @@ If **first time**, give a brief walkthrough before the interview:
 > Claude on Rails gives your Claude Code sessions a **session loop** —
 > a start and end routine that creates continuity between sessions.
 >
-> - **`/orient`** runs at the start. It reads where things stand — what
->   you were working on, what's due, what broke. Instead of starting
->   blind, Claude starts informed.
-> - **`/debrief`** runs at the end. It records what happened — what got
->   done, what's still open, what you learned. That's what orient reads
->   next time.
+> - **`/orient`** — you type this at the start of a session. It reads
+>   where things stand — what you were working on, what's due, what
+>   broke. Instead of starting blind, Claude starts informed.
+> - **`/debrief`** — you type this at the end of a session. It records
+>   what happened — what got done, what's still open, what you learned.
+>   That's what orient reads next time.
+>
+> Neither runs automatically — you invoke them when you're ready. If
+> you forget `/debrief`, Claude will nudge you before the session ends.
 >
 > Beyond the session loop, there are optional modules: **work tracking**
 > (a local task database), **planning** (structured plans with critique
@@ -55,10 +58,13 @@ Before asking any questions, read two global files if they exist:
    project fits into that."
 
 2. **`~/.claude/cor-registry.json`** — a list of all their CoR projects.
-   If they have other projects, ask how this one relates to them: "You
-   also have [project X] and [project Y]. Does this project connect to
-   either of those?" The answer goes into `_context.md` so orient and
-   debrief can reference sibling projects when relevant.
+   If they have other projects registered, explain what that means and
+   ask how this project relates: "I see you're also using Claude on
+   Rails in [project X] — that's a separate project you've set up with
+   the same session loop. Does this project connect to that one in any
+   way? For example, does one feed data to the other, or do they share
+   code?" The answer goes into `_context.md` so orient and debrief can
+   flag when work in one project might affect the other.
 
 If neither file exists, that's fine — the installer may not have created
 them (npm install path, or the user skipped the identity questions).