skills.rest
TheBushidoCollective
TheBushidoCollectiveOFFICIAL
Explore all skills by this author →
WebsiteGitHub

scratch-workspace

Set up a gitignored scratch workspace with structured subdirectories for temporary files.

187|20|Updated Nov 20, 2025
Search Tags:#draft#experiment#version-control#scratch#temporary
One-click install
npx skills add https://github.com/TheBushidoCollective/han --skill scratch-workspace
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: scratch-workspace
Source: https://github.com/TheBushidoCollective/han/tree/main/jutsu/jutsu-scratch/skills/scratch-workspace
Command: npx skills add https://github.com/TheBushidoCollective/han --skill scratch-workspace

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides using .claude/.scratch for draft code, experiments, and planning that should not be committed.

Core Features & Use Cases

  • Temporary Storage: Drafts and experiments outside version control.
  • Git Ignore: Ensure scratch stays out of commits.
  • Promotion Path: Move finalized work to proper project locations.

Quick Start

Create a scratch folder for an experimental feature and later promote it to the main codebase.

Frequently Asked Questions about scratch-workspace

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

FAQPage Schema
How do I keep draft code and experiments out of version control?▼

Draft code and experiments should reside in a dedicated scratch workspace outside version control. Use .claude/.scratch directory with gitignore verification to ensure temporary files, test data, and planning documents remain uncommitted while keeping your main codebase clean.

What's the best way to organize temporary files during development?▼

Organize temporary work in structured subdirectories within .claude/.scratch: drafts for incomplete features, experiments for exploratory code, notes for planning documents, and temp for intermediate artifacts. This separation makes it easy to identify and promote finalized work later.

How do I promote experimental code from scratch to my main project?▼

Once experimental code is proven and ready, move finalized work from .claude/.scratch subdirectories to proper project locations in your main codebase. Clean up scratch leftovers after promotion to maintain a clear separation between temporary and committed code.

Can I use a scratch workspace for version control workflows?▼

Yes. A scratch workspace is designed specifically for non-committable work in version control workflows. It provides a safe, gitignored area for drafts and experiments without interfering with your repository, making it ideal for iterative development and testing.

Do I need to manually set up gitignore for the scratch directory?▼

The scratch workspace includes gitignore verification to ensure .claude/.scratch stays out of commits automatically. Setup handles directory creation and gitignore configuration so temporary files are protected from accidental commits by default.

Related Skills

Explore More Personal & Entrepreneur Skills→
HomericIntelligenceHomericIntelligence
6

git-worktrees

Create isolated git worktrees with safety checks and cleanup workflows.

Official
Advanced
p-o-ke-naep-o-ke-nae

github-flow

Guide GitHub Flow branching, commits, testing, pull requests, and squash merges.

Community
Intermediate
117503445117503445
2

commit

Standardize Git commits by reviewing staged changes and sensitive information.

Community
Basic
thechandanbhagatthechandanbhagat
8

git

Automate Git branch, commit, merge, rebase, and stash operations.

Community
Advanced