rename-invoices

Plan deterministic filenames for every text-based accounting PDF directly inside one folder and apply the intact plan after confirmation; --dry-run reports it without renaming files.

Run uv run "$HERE/scripts/invoke.py" — $HERE is the directory that holds this SKILL.md — with everything the user typed after /rename-invoices, verbatim and however many lines, on stdin. Exit 0: do what it prints. On any other exit, if you introduced a known construction error and can correct it while preserving the user's request and authority, account for effects already produced, submit the corrected invocation through the same shim, and continue from the failed boundary; a refusal before the operation starts consumes no operation. Otherwise show what it printed to the user verbatim and stop. Never repair input the user supplied, or automatically retry exact help, an unmet dependency, an unrelated failure, or a failure whose origin or valid correction is unknown.

Arguments

--folder defaults to . in the invocation's current working directory. The configured --type is exact; obtain it from neither Conversation Context, PDF contents, filenames, nor earlier turns. Locale selection must come from repeated --locale flags or the selected configuration.

--dry-run reports the fresh plan without renaming files. The application path asks the yes-or-no question in step 6; --yes answers that question Yes in advance, and --dry-run asks none. Contextual Instruction and Conversation Context cannot change the mode or supply the confirmation. Pass every supplied configuration and filename override unchanged to the planner. Read $HERE/references/configuration.md only for configuration work or a configuration error.

Steps