ChatGPT AI Guide: Audit Kurta Image Filenames and Revisions

By TryBuy Editorial

Use ChatGPT to audit a text list of kurta image filenames and produce a proposed naming map. The model can help organise identifiers, view labels, production types and revisions, but this workflow does not rename files automatically. Review the proposed map against the real assets before using your normal file-management process to apply any approved change.

Prepare the filename inventory

Supply the existing filename and the known garment, source ID, view, production type and status for each asset. Preserve actual product identifiers exactly. If a file’s view or source is unknown, record that uncertainty rather than inferring it from a decorative name. Keep the original source photograph distinguishable from edits and generated concepts.

Add your preferred naming convention and its purpose. A small team may only need garment, view and revision, while another project needs a separate export label. Do not ask the model to invent a SKU or include unnecessary personal information. Keep detailed prompts and limitations in a manifest rather than forcing every fact into a very long filename.

Copy the naming-audit prompt

Audit my supplied filename inventory and propose a readable naming map. Return original filename, proposed filename, preserved garment identifier, view, production type, revision reason, status and unresolved field. Do not invent identifiers, infer unknown source relationships or rename any files. Flag collisions, ambiguous final labels and entries that appear to mix original photographs with concepts. Keep a separate manifest for details too long for the name, and preserve every original filename so I can review the proposal.

Ask for collision checking within the supplied list. The model cannot establish that a name is unique across folders or systems it has not been given. Keep that boundary visible before applying the map.

Filled fictional example

Imagine the fictional inventory contains final.jpg, final-new.jpg and product-a-front-r02.jpg. Only the third has a confirmed source and view. The proposed map should flag missing context for the first two instead of assigning them approved status from their names. A clear file name is an organisational aid, not proof that the image was reviewed.

For a confirmed asset, a name such as PRODUCT-A_FRONT_CONCEPT_R02 can illustrate a pattern. It is not a real catalogue identifier. The rename proposal should preserve the actual product code you supplied and keep the original-to-proposed relationship intact so a person can check the files before acting.

Refine the manifest with revisions

• “Show every proposed name whose garment, view or status was inferred rather than supplied.”
• “Keep source photographs outside the generated-concept naming group.”
• “List duplicate proposed names and ask which confirmed field can distinguish them.”

When a revision arrives, record the reason as well as the number. Correcting a sleeve outline and changing a background have different implications for review. Do not let a higher revision number automatically mean approved for every use.

Review before changing files

Match each row to the actual asset and verify the source relationship. Check the proposed names using the rules of your real storage environment, particularly where case or repeated characters may matter. Keep the approved selection separate from working versions without deleting history merely to make the folder look tidy. The model’s text proposal is not a completed file operation.

Use the original practical guide for the practical naming and handoff system and the men’s kurtas collection for current garment identity context. Save the original inventory, reviewed map and manifest together. The deliverable should make the next editor’s choices clearer while preserving traceability and leaving actual file actions under your control, rather than implying that a written naming plan has already reorganised the project.

For general instructions and follow-up techniques, see official OpenAI prompting guidance.