scratch-dir

Redirect temporary command output files to a gitignored scratch/ directory.

2|Updated Aug 18, 2025

Search Tags:#git #logs #temporary files #output #scratch #git ignore

Ready to run

npx skills add https://github.com/ESO-Toolkit/eso-toolkit --skill scratch-dir

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: scratch-dir
Source: https://github.com/ESO-Toolkit/eso-toolkit/tree/main/.github/skills/scratch-dir
Command: npx skills add https://github.com/ESO-Toolkit/eso-toolkit --skill scratch-dir

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents temporary command output files from cluttering your Git repository and polluting your git status.

Core Features & Use Cases

Organized Output: Redirects command output (lint results, logs, test dumps) to a dedicated, gitignored scratch/ directory.
Clean Git Status: Ensures your working directory remains clean by keeping temporary files out of Git's tracking.
Use Case: When running a lint command that produces a lot of output, redirect it to scratch/lint-output.txt instead of the root directory.

Quick Start

Use the scratch-dir skill to redirect the output of the 'npm run lint' command to a file in the scratch directory.

Frequently Asked Questions about scratch-dir

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

FAQPage Schema

How do I keep temporary command output files out of my Git status?▼

To keep temporary command output files out of your Git status, redirect ad-hoc outputs like lint results and debug dumps to a dedicated 'scratch/' directory that is automatically gitignored, ensuring your working directory remains clean.

What is the best way to manage ad-hoc command output in a Git repository?▼

The best way to manage ad-hoc command output is to redirect logs and test dumps into a gitignored 'scratch/' directory, which prevents these temporary files from cluttering your repository root and polluting version control tracking.

How do I redirect lint results to a temporary directory during CI processes?▼

You can redirect lint results to a temporary directory by pointing the output of commands like 'npm run lint' to a file such as 'scratch/lint-output.txt', keeping temporary CI logs safely out of Git's tracking.

Does the scratch-dir approach require any specific Git configuration or dependencies?▼

No specific Git configuration or dependencies are required. The approach works by simply redirecting your temporary files into a dedicated 'scratch/' directory that is handled as gitignored space within your existing repository.

Why does my Git status show untracked files when I run local debug dumps?▼

Your Git status shows untracked files because local debug dumps and temporary command output are written to the repository root, a problem solved by redirecting them to a gitignored 'scratch/' directory to maintain a clean working state.