fast

Plan, test, and push small fixes directly to main with GitHub issue tracking.

Updated Sep 21, 2025
One-click install
npx skills add https://github.com/jammindev/house --skill fast-jammindev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fast
Source: https://github.com/jammindev/house/tree/main/.claude/skills/fast
Command: npx skills add https://github.com/jammindev/house --skill fast-jammindev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you deliver a small fix or micro-feature quickly on the main branch while still keeping a clear GitHub issue trail and verification discipline.

Core Features & Use Cases

  • Rapid main-branch workflow: Handles the full path from understanding the request to proposing a solution, planning, tracking, implementing, and shipping.
  • Issue-first accountability: Creates a GitHub issue before coding so the change is documented, tracked, and later closed automatically.
  • TDD-oriented delivery: Encourages writing tests first, then implementing the minimum change, then validating everything is green before pushing.
  • Safe direct deployment: Suits isolated bug fixes, small enhancements, or other low-risk changes where bypassing a PR is explicitly acceptable.

Quick Start

Use the fast skill to analyze the request, propose a concise fix plan, create the tracking issue, implement the change with tests, and ship it on main once everything passes.

Frequently Asked Questions about fast

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

FAQPage Schema
How do I ship a small bug fix directly on the main branch fast?

To ship a bug fix fast on the main branch, use a rapid main-branch workflow that proposes a concise plan, creates a tracking issue, implements the change with tests, and pushes safely once verification passes.

Can I bypass pull requests for isolated micro-features and still maintain issue tracking?

Yes, you can bypass pull requests for isolated micro-features by creating a GitHub issue before coding, ensuring the change is documented and tracked, and closing the issue automatically after committing directly to main.

What is the best way to apply TDD for quick main-branch deployments?

The best way to apply TDD for quick main-branch deployments is to write tests first, implement the minimum required change, validate that all tests are green, and then execute a safe commit-and-push discipline.

When should I avoid direct deployment to main for software changes?

You should avoid direct deployment to main for software changes that are not isolated, involve high risk, or require collaborative review, as this approach is strictly suited for low-risk small enhancements and bug fixes.