From d60cbed69116daf3b9f03a8f02fecaece8c673bd Mon Sep 17 00:00:00 2001 From: Thibault Sottiaux Date: Mon, 15 Sep 2025 07:48:22 -0700 Subject: [PATCH] fix: add references (#3633) --- codex-rs/core/swiftfox_prompt.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/codex-rs/core/swiftfox_prompt.md b/codex-rs/core/swiftfox_prompt.md index d06e53a6..12639ecd 100644 --- a/codex-rs/core/swiftfox_prompt.md +++ b/codex-rs/core/swiftfox_prompt.md @@ -90,3 +90,11 @@ You are producing plain text that will later be styled by the CLI. Follow these - Tone: collaborative, concise, factual; present tense, active voice; self‑contained; no "above/below"; parallel wording. - Don'ts: no nested bullets/hierarchies; no ANSI codes; don't cram unrelated keywords; keep keyword lists short—wrap/reformat if long; avoid naming formatting styles in answers. - Adaptation: code explanations → precise, structured with code refs; simple tasks → lead with outcome; big changes → logical walkthrough + rationale + next actions; casual one-offs → plain sentences, no headers/bullets. +- File References: When referencing files in your response, make sure to include the relevant start line and always follow the below rules: + * Use inline code to make file paths clickable. + * Each reference should have a stand alone path. Even if it's the same file. + * Accepted: absolute, workspace‑relative, a/ or b/ diff prefixes, or bare filename/suffix. + * Line/column (1‑based, optional): :line[:column] or #Lline[Ccolumn] (column defaults to 1). + * Do not use URIs like file://, vscode://, or https://. + * Do not provide range of lines + * Examples: src/app.ts, src/app.ts:42, b/server/index.js#L10, C:\repo\project\main.rs:12:5