skills.rest
EvanPluchart
EvanPluchartCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

quick-dev

Implement small code fixes with auto-commit or dry-run modes.

2|Updated Mar 19, 2026
Search Tags:#workflow#verification#context loading#code change#dry-run#auto-commit#stack detection
One-click install
npx skills add https://github.com/EvanPluchart/kyomu --skill quick-dev-evanpluchart
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: quick-dev
Source: https://github.com/EvanPluchart/kyomu/tree/main/.claude/skills/quick-dev
Command: npx skills add https://github.com/EvanPluchart/kyomu --skill quick-dev-evanpluchart

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you implement a small, well-scoped code change quickly while avoiding the overhead of the full feature workflow.

Core Features & Use Cases

  • One-shot decisioning: Quickly decide whether a change is suitable for quick implementation (small, localized) or should be redirected to the full /feature-planner workflow.
  • Adaptive context loading: Load only the most relevant workflow documentation for the detected stack by reading the manifest and applying stack-specific scope rules.
  • Mode-based execution: Support direct implementation with optional auto-commit or a safe dry-run that describes intended changes.

Quick Start

Run this Skill in default mode to implement a small fix requested by the user and propose a single atomic commit message after verification.

Frequently Asked Questions about quick-dev

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

FAQPage Schema
How do I implement a small code fix without running the full feature-planning workflow?▼

You can implement small code fixes or features without the full feature-planner workflow by using a rapid development mode that handles localized refactors and bug fixes spanning only a few files, proposing an atomic commit after verification.

When should I use quick code changes instead of a full sprint-planner workflow?▼

Use quick code changes when the modification can be described in one to two phrases and is localized to a few files, such as straightforward bug fixes or small feature additions, redirecting larger changes to the full sprint-planner workflow.

How does adaptive context loading work for stack-specific code changes?▼

Adaptive context loading detects the project stack by reading the manifest and applying stack-specific scope rules to load only the most relevant workflow documentation before implementing the code change.

Can I dry-run a localized refactor before committing to verify nothing breaks?▼

Yes, you can use dry-run mode to describe intended changes safely without applying them, while post-change verification checks imports and tests to avoid breaking the project after a direct implementation and auto-commit.

What are the limitations of a rapid development approach for small bug fixes?▼

This rapid approach is limited to small, well-scoped changes spanning a few files; complex features requiring full planning, extensive refactoring, or multi-sprint coordination should be redirected to the complete feature-planning workflow instead.

Related Skills

Explore More Software Engineering Skills→
MileniumTickMileniumTick

sdd-init

Detect project tech stack and generate a local skill registry.

Community
Advanced
zrongzrong
11

git-commit

Format git commit messages, stage atomic changes, and generate CalVer tags.

Community
Advanced
masharrattmasharratt
14

context-injector-readme

Orchestrate container-based CFN Loop execution with agent spawning and consensus collection.

Community
Basic
kubrickcodekubrickcode
1

workflow-auto

Automate analyze, plan, execute, and commit workflow steps sequentially.

Community
Advanced