Best files to include
Start with models, views, serializers, templates, settings, URLs, migrations relevant to the issue, and tests. Add tests and docs when they explain expected behavior.
Workflow
Use Riflet to keep the bundle narrow and readable.
- Add your repo source.
- Select the route, feature, or module under discussion.
- Remove framework noise and generated output.
- Export the bundle and upload it to ChatGPT.
Limitations
ChatGPT still depends on the prompt and the included files. Riflet gives it the context; it does not execute tests or deploy code.
Avoid exporting every migration or virtualenv file. Include the migrations only when schema history matters.
Build your AI context file with Riflet
Select the sources that matter, check the token budget, and export one clean file for the AI you already use.
Download Riflet freeFrequently asked questions
Can I use this Django to ChatGPT bundle in more than one AI tool?
Yes. Riflet exports plain text or Markdown, so the same context file can be used in Claude, ChatGPT, Gemini, Perplexity, or a local model if that tool accepts pasted text or file uploads.
Does Riflet automatically update the AI after my files change?
No. Riflet is deliberately export-based. When your files change, reopen the workspace, let Riflet reapply the saved sources and filters, export a fresh bundle, and upload it where you want to use it.
How do I avoid giving ChatGPT too much context?
Start with the decision or task, then include only the files that would help a smart human answer it. Use Riflet's token count to remove stale, duplicated, generated, or background-only files before exporting.
Do my files leave my computer when Riflet builds the bundle?
Riflet processes selected files locally. Your content leaves your machine only if you choose to paste or upload the exported bundle into an AI product.