octopus-quick

Executes small ad-hoc code changes with atomic commits and summary tracking.

Updated Aug 15, 2026
One-click install
npx skills add https://github.com/GongYuanCaiJi/dsh-claude-octopus --skill octopus-quick-gongyuancaiji
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: octopus-quick
Source: https://github.com/GongYuanCaiJi/dsh-claude-octopus/tree/main/.claude/skills/skill-quick
Command: npx skills add https://github.com/GongYuanCaiJi/dsh-claude-octopus --skill octopus-quick-gongyuancaiji

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Full multi-AI workflows add unnecessary overhead for trivial tasks like typo fixes, config tweaks, or single-file bug fixes. This Skill provides a lightweight execution path that skips research, planning, and multi-provider validation while still keeping commits, state tracking, and summaries. ## Core Features & Use Cases - Fast-track execution: Implements small, well-understood changes directly without multi-AI orchestration. - Atomic commits with audit trail: Every change is committed with a quick: prefixed message, recorded in state, and summarized in .claude-octopus/quick/. - Escalation guidance: Detects when a task is too complex and recommends switching to the full Discover/Define/Develop/Deliver workflow. - Use Case: A user asks to fix a typo in README.md or update a dependency version; the Skill edits the file, commits the change, logs the decision, and writes a timestamped summary. ## Quick Start Ask the assistant to use quick mode to fix a small, known issue such as "fix the broken import in auth.ts" and it will edit, commit, and summarize the change.

Frequently Asked Questions about octopus-quick

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a quick fix without the full octopus workflow?▼

Invoke quick mode with a command like /octo:quick followed by a short task description, for example fixing a typo or updating a dependency. The change is implemented directly, committed atomically, and summarized without multi-AI research or validation.

What tasks are appropriate for quick mode execution?▼

Quick mode suits one-file bug fixes, typo corrections, config changes, small refactorings, documentation updates, and dependency management. It is meant for tasks with known solutions that take one to three minutes.

When should I not use quick mode for a code change?▼

Avoid quick mode for new features, architecture changes, multi-file refactorings, security-sensitive changes, and anything requiring research. Use the full Discover, Define, Develop, Deliver workflow for complex or risky work.

Does quick mode still track changes and commits?▼

Yes. Quick mode keeps atomic git commits with a quick: prefix, updates state via the state-manager script, and writes a timestamped summary file under .claude-octopus/quick/ for a full audit trail.

What happens if a quick task turns out to be complex?▼

The Skill instructs stopping and escalating to a full workflow when multiple files, architectural decisions, security implications, or research needs appear. It suggests the appropriate /octo command such as discover, define, develop, or deliver.