docs(FN-2432): refresh Fusion skill docs for current CLI and extension

- Update top-level Fusion skill guidance and capability descriptions to reflect current terminology and tool behavior
- Replace stale KB-* task examples with FN-* IDs across CLI reference, task structure, and workflow guides
- Refresh capability and workflow docs with current commands (including node runtime, skills, and comment guidance)
- Add a changeset for @runfusion/fusion documenting the shipped skill documentation refresh
This commit is contained in:
Fusion
2026-04-24 07:50:43 -07:00
committed by gsxdsm
parent 7616cf3cc5
commit 832c32c5ed
10 changed files with 71 additions and 75 deletions

View File

@@ -32,11 +32,11 @@ These cannot be done with pi extension tools:
| Operation | CLI Command | Dashboard |
|-----------|-------------|-----------|
| Move task to column | `fn task move KB-001 todo` | Drag card between columns |
| Merge completed task | `fn task merge KB-001` | Click merge in task detail |
| Add steering comment | `fn task steer KB-001 "Use TypeScript"` | Comments tab in task detail |
| Add general comment | `fn task comment KB-001 "Looks good"` | Comments tab in task detail |
| View agent logs | `fn task logs KB-001 --follow` | Agent log tab in task detail |
| Move task to column | `fn task move FN-001 todo` | Drag card between columns |
| Merge completed task | `fn task merge FN-001` | Click merge in task detail |
| Add steering comment | `fn task steer FN-001 "Use TypeScript"` | Comments tab in task detail |
| Add general comment | `fn task comment FN-001 "Looks good"` | Comments tab in task detail |
| View agent logs | `fn task logs FN-001 --follow` | Agent log tab in task detail |
| Change settings | `fn settings set maxConcurrent 4` | Settings modal |
| Create workflow steps | — | Workflow Steps button in header |
| Git operations | `fn git status/fetch/pull/push` | Git manager panel |
@@ -60,7 +60,7 @@ Key settings (configure via dashboard Settings or `fn settings set`):
When `prCompletionMode` is set to "pr-first":
- Completed tasks create a GitHub PR instead of direct-merging
- Use `fn task pr-create KB-001` to manually create a PR for any in-review task
- Use `fn task pr-create FN-001` to manually create a PR for any in-review task
- PRs can be reviewed and merged through the normal GitHub workflow
**Backup operations:**

View File

@@ -94,11 +94,11 @@ For large-scale projects spanning multiple tasks, use the mission hierarchy:
fn_slice_activate({ id: "SL-001" })
```
6. **Link features to tasks** — Connect features to kb tasks
6. **Link features to tasks** — Connect features to Fusion tasks
```
fn_task_create({ description: "Create user model with email, password hash, and timestamps" })
# → Created KB-101
fn_feature_link_task({ featureId: "F-001", taskId: "KB-101" })
# → Created FN-101
fn_feature_link_task({ featureId: "F-001", taskId: "FN-101" })
```
**Mission status flows automatically:**

View File

@@ -87,7 +87,7 @@ The AI triage agent sets the review level based on task complexity and risk asse
**Interpreting `fn_task_show` output:**
```
KB-042: Fix login validation
FN-042: Fix login validation
Column: In Progress · Size: M · Review: 2
Steps (2/5):

View File

@@ -29,7 +29,7 @@ Example:
```
fn_task_create({
description: "The login form doesn't validate email format before submission. Add client-side email validation that shows an inline error message when the email is invalid. Use the existing form validation pattern from the signup form.",
depends: ["KB-042"]
depends: ["FN-042"]
})
```