skills.rest
lgwanai
lgwanaiCOMMUNITY
Explore all skills by this author →
GitHub

gsd-fast

Execute trivial file or text edits inline without planning or subagents.

4|1|Updated Mar 22, 2026
Search Tags:#bash#typo fix#config change#small refactor#inline task#repo edits
One-click install
npx skills add https://github.com/lgwanai/openforce --skill gsd-fast-lgwanai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-fast
Source: https://github.com/lgwanai/openforce/tree/main/skills/gsd-fast
Command: npx skills add https://github.com/lgwanai/openforce --skill gsd-fast-lgwanai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes friction for very small, well-scoped changes by letting you execute a trivial task immediately in the current context instead of paying planning overhead.

Core Features & Use Cases

  • Inline execution: Perform one-step fixes like typo corrections, small refactors, or straightforward config edits.
  • Low overhead workflow: Avoid generating plans or spawning subagents for tasks that can be done quickly.
  • Safe scope guidance: Use it when the job can be described in one sentence and completed in under about two minutes.

Quick Start

Tell the system to make a small change, for example: "Fix the typo in README.md and update the wording to match the surrounding style."

Frequently Asked Questions about gsd-fast

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

FAQPage Schema
How do I make small refactors and config changes without generating a plan?▼

Inline execution performs small refactors and config changes directly in the current context without generating planning documents. It avoids spawning subagents, letting you complete one-sentence repo edits instantly without plan overhead.

What is the best way to do quick typo fixes in my code repository?▼

Quick typo fixes are best handled by inline execution in the current context, bypassing plan generation and subagent orchestration. This allows straightforward text modifications to finish within minutes without planning overhead.

Can I use inline execution for repo edits that take less than two minutes?▼

Yes, inline execution fits repo edits describable in one sentence and completable under two minutes. It safely handles small refactors, config changes, and typo corrections directly without spawning subagents or planning documents.

Why does my workflow generate a plan for one-sentence edits?▼

Your workflow generates plans due to default planning overhead for all tasks. Avoid this by using inline execution for one-sentence edits, which explicitly skips planning documents and subagent orchestration for trivial repo modifications.

When should I avoid inline execution for file modifications?▼

Avoid inline execution when a task cannot be described in one sentence or takes longer than two minutes. If the job requires complex planning, subagent orchestration, or extensive refactoring, use a standard planning workflow instead.

Related Skills

Explore More Software Engineering Skills→
deerawandeerawan
1

gsd-fast

Execute small edits and configuration changes directly without plan files.

Community
Basic
kirvinkirvin

commit

Stage Git changes and create conventional commit messages with preflight checks.

Community
Intermediate
wellnessbrotherjay-debugwellnessbrotherjay-debug

Command Development

Create Claude Code slash commands with YAML frontmatter and bash execution.

Community
Advanced
joaquimscostajoaquimscosta
21

workflow-orchestration

Coordinate multi-agent parallel execution for complex multi-step tasks.

Community
Advanced