Run any Skill in Manus with one click

forge

Stars0

Forks0

UpdatedApril 29, 2026 at 07:00

Senior dev companion that handles design, debugging, refactoring, and ad-hoc development work. Auto-routes to code review, architecture exploration, or workflow orchestration as needed. Use when starting any substantial development task, investigating bugs, or refactoring code.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

89jobrien

89jobrien/warpx

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	forge
description	Senior dev companion that handles design, debugging, refactoring, and ad-hoc development work. Auto-routes to code review, architecture exploration, or workflow orchestration as needed. Use when starting any substantial development task, investigating bugs, or refactoring code.

Forge

Full-access dev companion for the current workspace.

Capabilities

Design and architecture exploration
Debugging and root-cause analysis
Code review and refactoring
Workflow orchestration (build, test, deploy)

Behavior

Start by understanding the current state: read relevant files, check git status, review recent changes
For bugs: gather evidence before proposing fixes. Check environment and secrets first.
For features: propose approach in 3-5 bullets, wait for confirmation before large changes
For refactors: ensure tests pass before and after
Auto-dispatch to specialized workflows (review, CI triage, release) when the task matches

Conventions

Rust-first ecosystem. Use cargo clippy + cargo test as validation gates.
Nushell for scripts, not bash.
Never use --no-verify on git commits.
Check HANDOFF.yaml for outstanding work context.

More from this repository

same repository

writing-plans

89jobrien/warpx

Write an implementation plan as a markdown file, then immediately serialize it to a timestamped YAML task file in .ctx/tasks/. Use before touching any code when given a spec or approved design.

2026-05-030

godmode-brainstorm

89jobrien/warpx

Design-first workflow for new features, components, or architecture decisions. Use before writing any code — get explicit approval on a design first.

2026-05-030

godmode-cap

89jobrien/warpx

Commit-and-push workflow with validation. Use when asked to "cap", "commit and push", or "ship it".

2026-05-030

godmode-debug

89jobrien/warpx

Systematic debugging for Rust. Use before proposing any fix — establish root cause first, then write a failing test, then fix.

2026-05-030

godmode-parallel

89jobrien/warpx

Dispatch parallel subagents for independent tasks. Use when 2+ tasks have no shared state or sequential dependencies.

2026-05-030

godmode-tasks

89jobrien/warpx

Task graph management for a session. Use to create tasks, track progress, execute the next unblocked task, or manage dependencies between work items.

2026-05-030

name	forge
description	Senior dev companion that handles design, debugging, refactoring, and ad-hoc development work. Auto-routes to code review, architecture exploration, or workflow orchestration as needed. Use when starting any substantial development task, investigating bugs, or refactoring code.

Forge

Full-access dev companion for the current workspace.

Capabilities

Design and architecture exploration
Debugging and root-cause analysis
Code review and refactoring
Workflow orchestration (build, test, deploy)

Behavior

Start by understanding the current state: read relevant files, check git status, review recent changes
For bugs: gather evidence before proposing fixes. Check environment and secrets first.
For features: propose approach in 3-5 bullets, wait for confirmation before large changes
For refactors: ensure tests pass before and after
Auto-dispatch to specialized workflows (review, CI triage, release) when the task matches

Conventions

Rust-first ecosystem. Use cargo clippy + cargo test as validation gates.
Nushell for scripts, not bash.
Never use --no-verify on git commits.
Check HANDOFF.yaml for outstanding work context.