create-claude-rails 0.5.5 → 0.5.6
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -88,17 +88,44 @@ points to a local path rather than a `node_modules` path):
|
|
|
88
88
|
- Add frontmatter: `type: field-feedback`, `source: [project]`,
|
|
89
89
|
`date: [ISO date]`, `component: [skill/phase name]`
|
|
90
90
|
|
|
91
|
-
**If not linked
|
|
92
|
-
|
|
93
|
-
|
|
94
|
-
-
|
|
95
|
-
|
|
96
|
-
|
|
97
|
-
|
|
98
|
-
|
|
99
|
-
|
|
100
|
-
|
|
101
|
-
|
|
91
|
+
**If not linked**, check whether `gh` is available and authenticated
|
|
92
|
+
(`gh auth status` exits 0). Then present the user with their options:
|
|
93
|
+
|
|
94
|
+
- **If `gh` works**, offer two choices:
|
|
95
|
+
> "I can send this as a GitHub issue so the developer sees it
|
|
96
|
+
> directly, or save it locally. Which do you prefer?"
|
|
97
|
+
>
|
|
98
|
+
> 1. Send as GitHub issue
|
|
99
|
+
> 2. Save locally (I'll send it later or pass it along myself)
|
|
100
|
+
|
|
101
|
+
If they choose GitHub:
|
|
102
|
+
- Open a GitHub issue on `orenmagid/claude-on-rails`
|
|
103
|
+
- Title: `Field feedback: [short title]`
|
|
104
|
+
- Label: `field-feedback` (create if needed)
|
|
105
|
+
- Body: the feedback markdown
|
|
106
|
+
|
|
107
|
+
- **If `gh` is not available** (most common for non-developers):
|
|
108
|
+
> "I'll save this feedback locally for now. If you want, you can
|
|
109
|
+
> pass it along to the developer yourself, or set up a free GitHub
|
|
110
|
+
> account so future feedback goes directly to them. Here's a guide
|
|
111
|
+
> if you're interested:
|
|
112
|
+
> https://github.com/orenmagid/claude-on-rails/blob/main/GITHUB-SETUP.md
|
|
113
|
+
> — totally optional. Your feedback is saved either way."
|
|
114
|
+
|
|
115
|
+
Only show the GitHub setup suggestion the first time. Track whether
|
|
116
|
+
it's been shown by checking for a `cor-feedback-gh-prompted` key
|
|
117
|
+
in `.corrc.json`. After the first time, just say "Saved locally."
|
|
118
|
+
|
|
119
|
+
**For either local save path:**
|
|
120
|
+
|
|
121
|
+
- Append the feedback to `~/.claude/cor-feedback-outbox.json` as a
|
|
122
|
+
JSON array entry with fields: `source` (project name), `date`,
|
|
123
|
+
`component`, `title`, `body`, `status: "pending"`
|
|
124
|
+
- Create the file if it doesn't exist (initialize with `[]`)
|
|
125
|
+
|
|
126
|
+
**Flushing the outbox:** If a user later sets up `gh` and asks to
|
|
127
|
+
send saved feedback, read the outbox, post each `pending` entry as
|
|
128
|
+
a GitHub issue, and update its status to `"sent"` with the issue URL.
|
|
102
129
|
|
|
103
130
|
### 5. Done
|
|
104
131
|
|