Runfusion
Review Skills published by Runfusion, their source repositories, maintenance signals, and identity status.
- Skills
- 7
- Repository stars
- 1,142
- Identity status
- Source-linked
Provenance
Source and identity
- Profile type
- Creator
- Canonical name
- Runfusion
- Public sources
- 1
- License context
- MIT
Source entries
Agent Skills from Runfusion
Repository stars and maintenance signals provide context, but do not automatically become an individual Skill's quality score.
Runfusion/Fusion
ce-brainstorm
Explore vague or ambitious ideas into a right-sized requirements-only unified plan. Use when the user wants to brainstorm, think through scope, decide what to build, or needs collaborative product framing before planning.
Runfusion/Fusion
ce-code-review
Structured code review for bugs, regressions, tests, and standards. Use before PRs or when asked for review; interactive mode can fix locally, while mode:agent reports only for pipeline callers.
Runfusion/Fusion
ce-compound
Document a recently solved problem or durable project vocabulary in docs/solutions/ or CONCEPTS.md. Use when capturing a learning after work.
Runfusion/Fusion
ce-debug
Diagnosis loop for bugs and failing behavior. Use for errors, stack traces, regressions, failed tests, issue-tracker bugs, stuck investigations after failed fixes, or asks to debug/fix a bug.
Runfusion/Fusion
ce-ideate
Generate and evaluate grounded ideas. Use when the user asks for ideas, improvements, surprising options, or AI-generated directions before choosing one to develop; use ce-brainstorm to refine the user's own idea.
Runfusion/Fusion
ce-plan
Create structured plans for multi-step work, including software and non-software tasks. Use when asked to plan, break down implementation, plan from requirements, or deepen an existing plan; prefer ce-brainstorm for exploratory framing.
Runfusion/Fusion
ce-work
Execute a plan or concrete work prompt end-to-end. Use when implementing from docs/plans, a spec path, or a clear build request; use ce-debug for open-ended bugs.
Pinned paths
Every entry links to a specific source path and commit when available.
Repository context
Activity, license, and repository-level popularity are shown as context.
Open the source
Inspect the public repository