forge-cc 0.1.24 → 0.1.25
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/forge-go.md +9 -9
package/package.json
CHANGED
package/skills/forge-go.md
CHANGED
|
@@ -362,12 +362,12 @@ Check for the Linear project ID in this priority order:
|
|
|
362
362
|
|
|
363
363
|
If a Linear project ID is found:
|
|
364
364
|
|
|
365
|
-
1. Transition issues for the completed milestone
|
|
366
|
-
- If this was the **last milestone**:
|
|
365
|
+
1. **Transition issues** for the completed milestone:
|
|
366
|
+
- If this was the **last milestone**: use `mcp__linear__update_issue` on each issue to set state to "In Review"
|
|
367
367
|
- Otherwise: keep issues as-is (they were set to "In Progress" at start)
|
|
368
368
|
|
|
369
|
-
2. If this is the **last milestone**, also:
|
|
370
|
-
-
|
|
369
|
+
2. If this is the **last milestone**, **also transition the project itself** (separate from issues):
|
|
370
|
+
- Use `mcp__linear__update_project` to set the project state to "In Review". **Do not skip this — the project is a separate entity from its issues.**
|
|
371
371
|
- Create a PR (see Step 8)
|
|
372
372
|
|
|
373
373
|
If no Linear project ID is found in either location, skip this step silently.
|
|
@@ -514,12 +514,12 @@ At the START of milestone execution (between Step 2 and Step 3), check for the L
|
|
|
514
514
|
1. `linearProjectId` field in `.planning/status/<slug>.json`
|
|
515
515
|
2. `linearProject` field in `.forge.json`
|
|
516
516
|
|
|
517
|
-
If a Linear project ID is found
|
|
517
|
+
If a Linear project ID is found, **execute ALL four steps below — do not skip any**:
|
|
518
518
|
|
|
519
|
-
1. Find issues associated with this milestone
|
|
520
|
-
2. Transition
|
|
521
|
-
3. Transition the project to "In Progress"
|
|
522
|
-
4. Add
|
|
519
|
+
1. **Find issues:** Use `mcp__linear__list_issues` with the project ID to find issues associated with this milestone.
|
|
520
|
+
2. **Transition issues:** Use `mcp__linear__update_issue` on each issue to set state to "In Progress".
|
|
521
|
+
3. **Transition the project:** Use `mcp__linear__update_project` to set the project state to "In Progress". **This is a separate step from transitioning issues — do not skip it.** The project and its issues are independent entities in Linear.
|
|
522
|
+
4. **Add comment:** Use `mcp__linear__create_comment` on each milestone issue with the body: "Starting execution via forge:go."
|
|
523
523
|
|
|
524
524
|
If no Linear project ID is found, skip silently.
|
|
525
525
|
|