Simplify the ai-tools CLI (#58066)

Author: sarahs

package.json

@@ -12,7 +12,7 @@
   "exports": "./src/frame/server.ts",
   "scripts": {
     "add-content-type": "tsx src/content-render/scripts/add-content-type.ts",
-    "ai-edit": "tsx src/ai-editors/scripts/ai-edit.ts",
+    "ai-tools": "tsx src/ai-tools/scripts/ai-tools.ts",
     "all-documents": "tsx src/content-render/scripts/all-documents/cli.ts",
     "analyze-text": "tsx src/search/scripts/analyze-text.ts",
     "analyze-comment": "tsx src/events/scripts/analyze-comment-cli.ts",

src/ai-editors/prompts/versioning-editor.prompt.yml

@@ -1,25 +1,32 @@
-# AI-powered editors
+# AI-powered tools
 
 A CLI tool for using AI to edit documentation according to defined prompts.
 
-This tool runs an AI review of content files based on an (extensible) set of prompt-driven guidelines. The default is versioning. In the future we might add: scannability, readability, style, technical accuracy.
+This tool refines content files using AI based on an (extensible) set of prompt-driven guidelines. The default is versioning refinement. In the future we might add: scannability, readability, style, technical accuracy.
 
 This script calls the [Models API](https://docs.github.com/en/rest/models/inference?apiVersion=2022-11-28#run-an-inference-request). It requires a personal access token with Models scopes in your `.env` file.
 
 ## Usage
 
 ```sh
-tsx src/ai-editors/scripts/ai-edit.js --editor <type> --response <type> --files <file1.md>
+# Direct command
+tsx src/ai-tools/scripts/ai-tools.ts --refine <type> --files <file1.md>
+
+# Or via npm script
+npm run ai-tools -- --refine <type> --files <file1.md>
 ```
 
 * `--files, -f`: One or more content file paths to process (required).
-* `--response, -r`: Specify the AI response format. Options: `rewrite` (default), `list`, `json`.
-* `--editor, -e`: Specify one or more editor types (default: `versioning`).
+* `--refine, -r`: Specify one or more refinement types (default: `versioning`).
 
-**Example:**
+**Examples:**
 
 ```sh
-tsx src/ai-editors/scripts/ai-edit.js --files content/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo.md --editor versioning --response list
+# Direct command
+tsx src/ai-tools/scripts/ai-tools.ts --files content/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo.md --refine versioning
+
+# Via npm script  
+npm run ai-tools -- --files content/copilot/tutorials/coding-agent/get-the-best-results.md --refine intro
 ```
 
 ## Requirements

src/ai-editors/scripts/ai-edit.ts

@@ -0,0 +1,9 @@
+messages:
+  - role: system
+    content: >-
+      {{markdownPrompt}}
+  - role: user
+    content: >-
+      Review this content file according to the provided system prompt.
+      {{input}}
+model: openai/gpt-5

src/ai-editors/README.md src/ai-tools/README.mdsrc/ai-editors/README.md renamed to src/ai-tools/README.md

@@ -0,0 +1,35 @@
+Your task is to remove the conditional markup from content files that looks like {% ifversion fpt or ghec %}Foo{% endif %}.
+
+You need to first try to write the content without any versioning at all, so it still makes sense to customers without causing confusion. If you need to explain versioning  differences, do so using prose.
+
+Here are the prose guidelines to follow:
+
+* For versioning at the article level:
+  - When the feature is only available in certain products, use the "Who can 
+  use this feature?" box to convey the content of this article applies only 
+  to XYZ products.
+  - When an article only exists before the functionality is in older versions 
+  of GHES (and not dotcom and newer versions of GHES), just remove that article. 
+  (This is akin to declining to document a feature.)
+
+* For versioning at the heading level:
+  - Use prose similar to the "Who can use this feature?" to convey that the 
+  content of this section applies only to XYZ products.
+
+* For versioning the paragraph or sentence level:
+  - Use one of the following content strategies:
+    - If you're briefly introducing a feature and then linking to an article, 
+    there's no need to specify versioning. Let folks learn availability when 
+    they follow the link, via the "Who can use this feature?" box.
+    - When necessary, start sentences with "With GitHub Enterprise Cloud...",
+    "On GitHub.com", "With GitHub Enterprise Server 3.15+..." etc.
+    - End list items with "(GitHub Enterprise Cloud only)", "(GitHub.com only)", etc.
+
+Review this content according to the versioning guideline above. Edit the versioning only. 
+
+**IMPORTANT OUTPUT FORMAT:**
+- Return the complete, updated file content (including frontmatter)
+- Make ONLY the versioning changes specified above
+- Do NOT add explanatory text before or after the content
+- Do NOT wrap the output in markdown code blocks
+- Output should be ready to write directly to the original file