the-frame-ai 0.11.0 → 0.11.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
CHANGED
|
@@ -24,6 +24,8 @@ Update `.planning/STATE.md`:
|
|
|
24
24
|
|
|
25
25
|
Read `package.json` (or `requirements.txt`, `Cargo.toml`, `go.mod`), `.planning/MAP.md`, `.frame/config.json`.
|
|
26
26
|
|
|
27
|
+
Read `language` field from `.frame/config.json`. All output to the user and the final report must be written in that language (e.g. `ru` → Russian, `en` → English). If `language` is `auto` or missing — use English.
|
|
28
|
+
|
|
27
29
|
Determine:
|
|
28
30
|
- **Runtime**: Node.js / Python / Go / Rust / Java
|
|
29
31
|
- **Framework**: React / Next.js / Vue / Nuxt / Svelte / Express / FastAPI / Django / etc.
|
|
@@ -23,6 +23,8 @@ If `.frame/config.json` missing → STOP: "❌ Run /frame:init first."
|
|
|
23
23
|
|
|
24
24
|
If `PERF_REPORT.md` missing → STOP: "❌ No performance report found. Run /frame:perf-audit first."
|
|
25
25
|
|
|
26
|
+
Read `language` field from `.frame/config.json`. All output to the user must be written in that language. If `language` is `auto` or missing — use English.
|
|
27
|
+
|
|
26
28
|
### Step 1: Read Report
|
|
27
29
|
|
|
28
30
|
Read `.planning/reports/performance/PERF_REPORT.md`.
|
|
@@ -35,45 +37,26 @@ Parse issues based on `$ARGUMENTS`:
|
|
|
35
37
|
|
|
36
38
|
Output: "Found {N} issues to fix: {list of IDs and titles}."
|
|
37
39
|
|
|
38
|
-
### Step 2: For Each Issue —
|
|
40
|
+
### Step 2: For Each Issue — Apply Fix
|
|
39
41
|
|
|
40
42
|
For each issue in the list:
|
|
41
43
|
|
|
42
44
|
1. Read the file mentioned in the issue (`File: path/file.ts:42`)
|
|
43
45
|
2. Understand the surrounding context (±20 lines)
|
|
44
|
-
3.
|
|
46
|
+
3. Apply the fix immediately
|
|
45
47
|
|
|
46
|
-
|
|
48
|
+
Output before applying:
|
|
47
49
|
|
|
48
50
|
```
|
|
49
51
|
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
|
50
52
|
[PERF-1] {title}
|
|
51
53
|
File: path/file.ts:42
|
|
52
|
-
|
|
53
|
-
Impact: {impact from report}
|
|
54
|
-
|
|
55
|
-
Proposed fix:
|
|
56
|
-
{description of what will change — 2-3 sentences}
|
|
57
|
-
|
|
58
|
-
--- BEFORE ---
|
|
59
|
-
{relevant code snippet}
|
|
60
|
-
|
|
61
|
-
--- AFTER ---
|
|
62
|
-
{fixed code snippet}
|
|
54
|
+
Applying fix: {description of what will change — 1 sentence}
|
|
63
55
|
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
|
64
|
-
Apply this fix? [y/n/skip]
|
|
65
56
|
```
|
|
66
57
|
|
|
67
|
-
Wait for user confirmation before applying.
|
|
68
|
-
|
|
69
|
-
- `y` → apply the fix, mark as done
|
|
70
|
-
- `n` → stop entirely
|
|
71
|
-
- `skip` → skip this issue, move to next
|
|
72
|
-
|
|
73
58
|
### Step 3: Apply Fix
|
|
74
59
|
|
|
75
|
-
After confirmation:
|
|
76
|
-
|
|
77
60
|
1. Apply the code change to the file
|
|
78
61
|
2. Run type check if available:
|
|
79
62
|
```bash
|
|
@@ -120,8 +103,8 @@ Update `.planning/STATE.md`:
|
|
|
120
103
|
|
|
121
104
|
## Rules
|
|
122
105
|
|
|
123
|
-
- **ALWAYS show
|
|
124
|
-
- **
|
|
106
|
+
- **ALWAYS show what's being fixed** before applying (issue ID, file, one-line description)
|
|
107
|
+
- **NEVER ask confirmation** — apply all found issues automatically
|
|
125
108
|
- **ALWAYS run typecheck + tests** after each fix
|
|
126
109
|
- **REVERT on failure** — if tests break, undo the change immediately
|
|
127
110
|
- **NEVER fix test files** — only production code
|