How /reset Distinguishes Between Profile Data, Documents Folder, and Full Wipe Operations in AI-Job-Search

The /reset command parses the $ARGUMENTS variable to detect three distinct scopes—profile, documents, or all—and executes targeted deletion or overwrite operations only after requiring explicit user confirmation.

Managing your job search data in the MadsLorentzen/ai-job-search repository requires precise control over what gets deleted. The /reset command provides granular scope-based operations defined in .claude/commands/reset.md that cleanly separate candidate profile metadata from uploaded documents, ensuring you never accidentally wipe critical data when you only intended to clear one category.

Scope-Based Argument Parsing

The command logic in .claude/commands/reset.md begins by examining $ARGUMENTS for one of three specific keywords that determine the operational scope:

• profile – Targets only the four skill files containing candidate data
• documents – Targets only user-provided files under the documents/ directory tree
• all – Executes both profile and documents reset operations sequentially

If arguments are missing or unrecognized, the command enters interactive mode, prompting the user to specify which scope they want before proceeding.

Profile-Only Reset Operation

When the profile scope is selected, /reset targets specific markdown files within the job application assistant framework. According to the source code in .claude/commands/reset.md (lines 37-62), this operation affects exactly four files:

1. 01-candidate-profile.md
2. 02-behavioral-profile.md
3. 05-cv-templates.md
4. 07-interview-prep.md

Before execution, the command enumerates each file and indicates whether it currently contains content. The reset operation overwrites these files with minimal "blank-template" markdown, preserving the surrounding framework structure while clearing personal data.

Documents-Only Reset Operation

The documents scope performs a surgical cleanup of user-uploaded assets without touching profile metadata. As implemented in .claude/commands/reset.md (lines 69-88), this mode globs every file under the documents/ sub-folders including:

• documents/cv/
• documents/linkedin/
• documents/diplomas/
• documents/references/
• documents/applications/

The command generates a tree view preview of all targeted files, then executes a series of rm commands that delete only the file contents while preserving the directory structure and the critical documents/README.md instruction file.

Full Wipe and Confirmation Safety

The all scope combines both operations, presenting a unified list of profile files and document trees before execution. Regardless of scope, the command implements a mandatory safety gate: users must literally type RESET in all caps to proceed. Any other input aborts the operation immediately.

Practical Usage Examples

# Reset only the candidate-profile data (preserves documents)

/reset profile

# Reset only the documents folder (preserves profile data)

/reset documents

# Full wipe – clears both profile data and all documents

/reset all

Each command displays the specific impact summary, requests confirmation, and reports post-reset status before advising next steps such as running /setup again.

Summary

• The /reset command distinguishes operations by parsing the $ARGUMENTS variable for profile, documents, or all keywords defined in .claude/commands/reset.md.
• Profile reset overwrites four specific skill files (01-candidate-profile.md, 02-behavioral-profile.md, 05-cv-templates.md, 07-interview-prep.md) with blank templates while preserving framework integrity.
• Documents reset deletes files within documents/cv/, documents/linkedin/, documents/diplomas/, documents/references/, and documents/applications/ but preserves the directory structure and documents/README.md.
• Full wipe (all) executes both scopes simultaneously after showing combined impact details.
• All operations require explicit confirmation by typing the literal word RESET to prevent accidental data loss.

Frequently Asked Questions

What files are deleted when I run /reset profile?

The profile scope clears four specific markdown files in .claude/skills/job-application-assistant/: 01-candidate-profile.md, 02-behavioral-profile.md, 05-cv-templates.md, and 07-interview-prep.md. These files are overwritten with minimal blank templates rather than deleted entirely, preserving the file structure required by the framework.

Does /reset documents delete the entire documents folder?

No. The documents scope deletes only the files within the subdirectories (cv, linkedin, diplomas, references, applications) while preserving the folder structure itself. It also specifically excludes documents/README.md from deletion, ensuring instructional documentation remains intact.

What happens if I run /reset without specifying a scope?

If the $ARGUMENTS variable contains no recognized scope keyword, the command enters interactive mode and prompts you to specify whether you want to reset profile, documents, or all. The operation cannot proceed without this explicit scope selection.

How does the confirmation process prevent accidental data loss?

Before any deletion occurs, the command displays an exact enumeration of affected files and requires you to type the literal string RESET in all caps. Any other input, including pressing Enter or typing lowercase "reset", aborts the operation immediately, creating a deliberate speed bump against accidental execution.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}