← ClaudeAtlas

templisted

Make temporary code changes for testing that can be easily undone. Use when user says "temp", "temporary change", "temporarily enable/disable/show/hide", or needs to force a UI state, bypass a guard, or flip a feature flag for local testing. Also handles "temp undo" to revert all temporary changes, and "temp list" to show them.
nielsmadan/skills · ★ 0 · Testing & QA · score 75
Install: claude install-skill nielsmadan/skills
<!-- Generated from https://github.com/nielsmadan/agentic-coding — edits here are overwritten. --> # Temp Make quick, reversible code changes for local testing. Every change is marked with a `TEMP:` comment so it can be found and undone later. ## Modes ### 1. Make a temporary change (default) Usage: `temp always show questionnaire` 1. Search the codebase for code related to the user's description. 2. Make the **minimal** change needed — flip a boolean, comment out a guard, force a condition, hardcode a value. Prefer the smallest diff possible. 3. Mark every modified line with a comment containing `TEMP:` and the reason. Use the appropriate comment syntax for the language. **Marking rules:** - Add `// TEMP: <reason>` (or `# TEMP:`, `/* TEMP: */`, `-- TEMP:`, etc.) at the end of each changed line, or on the line above if end-of-line isn't practical. - If commenting out code, wrap it like: ``` // TEMP: always show questionnaire — commented out guard // if (!hasSeenQuestionnaire) { ``` - If changing a value: ``` const showOnboarding = true; // TEMP: always show onboarding (was: false) ``` - Always include what the original value was when replacing a value, using `(was: ...)`. 4. Tell the user what was changed and how to undo (`temp undo`). ### 2. Undo all temporary changes Usage: `temp undo` 1. Grep the project for `TEMP:` markers. 2. If no markers found, tell the user there are no temporary changes. 3. For each file with markers, use `git checkout` or `g