polyforgeai 0.1.0 → 0.1.2
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 +1 -1
- package/skills/init/SKILL.md +5 -2
package/package.json
CHANGED
package/skills/init/SKILL.md
CHANGED
|
@@ -48,6 +48,7 @@ Scan the project root and detect:
|
|
|
48
48
|
### Existing Configuration
|
|
49
49
|
- Check for existing `CLAUDE.md`, `.claude/` directory, `docs/` folder
|
|
50
50
|
- If PolyForge was previously initialized: detect `.claude/polyforge.json`
|
|
51
|
+
- If `.claude/` exists with commands, skills, or other config (not from PolyForge): back it up entirely to `tmp/backup-{date}/.claude/` and start fresh. This avoids conflicts between old commands/skills and PolyForge. Inform the user: "Backed up existing `.claude/` to `tmp/backup-{date}/` — PolyForge will recreate it cleanly."
|
|
51
52
|
|
|
52
53
|
## Phase 2: Interactive Questions (ONE AT A TIME)
|
|
53
54
|
|
|
@@ -60,7 +61,7 @@ Suggested question flow (skip any already answered by detection):
|
|
|
60
61
|
3. "For issue tracking, I detected [tracker]. Is this where issues should be created?"
|
|
61
62
|
4. "What level of autonomy do you want for automated fixes? (a) Full auto — branch, fix, test, PR (b) Semi-auto — propose fix, wait for approval, then PR"
|
|
62
63
|
5. **Only if "full auto" was chosen in Q4**: "Do you want to allow Claude to execute all operations without asking permission (file edits, shell commands, etc.)? ⚠️ WARNING: This grants full access to read, write, and execute anything in this project directory. This is convenient for autonomous work but removes all safety prompts. (a) Yes — generate `.claude/settings.json` with full permissions (b) No — I'll approve operations manually"
|
|
63
|
-
- If (a):
|
|
64
|
+
- If (a): **CREATE `.claude/settings.json` IMMEDIATELY** — do not wait for Phase 3. This file must be written right now so that all subsequent file operations during init are auto-approved:
|
|
64
65
|
```json
|
|
65
66
|
{
|
|
66
67
|
"permissions": {
|
|
@@ -122,7 +123,8 @@ Generate based on detected stack. Include:
|
|
|
122
123
|
- Build/test/lint commands
|
|
123
124
|
- `@` references to detailed docs
|
|
124
125
|
- Key conventions detected
|
|
125
|
-
- PolyForge commands
|
|
126
|
+
- PolyForge commands (use these exact names):
|
|
127
|
+
`/init`, `/pr-review`, `/analyse-db`, `/analyse-code`, `/report-issue`, `/fix`, `/fix-ci`, `/brainstorm`, `/generate-doc`
|
|
126
128
|
|
|
127
129
|
If a `CLAUDE.md` already exists:
|
|
128
130
|
- Ask: "A CLAUDE.md already exists. (a) Merge PolyForge config into it (b) Keep it and create `.claude/rules/polyforge.md` instead (c) Replace it (backup saved to `tmp/`)"
|
|
@@ -139,6 +141,7 @@ Create if missing. Add to `.gitignore` if not already there.
|
|
|
139
141
|
## Context Management
|
|
140
142
|
|
|
141
143
|
- After generating all config files, present a summary of what was created and their locations
|
|
144
|
+
- When listing available commands, use the exact slash command names: `/init`, `/pr-review`, `/analyse-db`, `/analyse-code`, `/report-issue`, `/fix`, `/fix-ci`, `/brainstorm`, `/generate-doc` — never prefix with `polyforge-`
|
|
142
145
|
- Do not keep raw scan data in context — extract what's needed and discard
|
|
143
146
|
|
|
144
147
|
## Important Behaviors
|