Feat/add vs code insiders

[m-schaller-3]

Why?

Adds support for VS Code Insiders for agent platform detection

What Changed?

Mirrored config for vs-code in config scripts for detection

Testing

• In-code automated testing
• Tested on local mac (windows tester needed)

Checklist

• Ran tests and all pass
• Ran linters/hooks: pre-commit run --all-files
• Updated documentation if behavior changed
• Followed conventional commit message format

Summary by CodeRabbit

• New Features

  • Added VS Code Insiders as a supported tool with platform-specific prompt/install paths for Linux, macOS, and Windows.

• Documentation

  • Updated guides and specs to document VS Code Insiders configuration, installation directories, coexistence with VS Code, and verification notes.

• Tests

  • Added/updated unit and integration tests to cover VS Code Insiders detection, path resolution, and end-to-end generation checks.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR adds VS Code Insiders as a supported agent: new configuration entry with platform-specific command/detection paths, unit and integration tests to validate detection and generation, and comprehensive documentation/specs/proofs describing the addition and verification artifacts.

Changes

Cohort / File(s)	Summary
Configuration slash_commands/config.py	Added vs-code-insiders entry to _SUPPORTED_AGENT_DATA mirroring VS Code with platform-specific command directories, detection paths, and .prompt.md extension.
Unit Tests tests/test_detection.py, tests/test_config.py	Added parametrized platform tests for VS Code Insiders (linux/darwin/win32), detection-present/absent cases, and extended detection_dirs coverage for the Insiders agent.
Integration Tests tests/integration/test_generate_command.py	Included "vs-code-insiders" in the agents list for test_generate_all_supported_agents; test loop and assertions reused for the new agent.
Documentation README.md, docs/slash-command-generator.md	Inserted VS Code Insiders entries and a dedicated section with per-OS prompt directory paths; clarified that VS Code and VS Code Insiders use independent prompt directories.
Specs & Proofs docs/specs/08-spec-vs-code-insiders-support/*	Added spec, tasks, validation, questions, and multiple proof artifact files documenting design, tests, integration behavior, and verification output for VS Code Insiders support.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

• feat(agents): add Amazon Q support and improve test maintainability #13 — Adds a new agent entry to _SUPPORTED_AGENT_DATA, similar pattern for extending supported agents.
• feat(config): add cross-platform VS Code detection for macOS and Windows #14 — Introduces VS Code Insiders configuration and tests that reuse platform-specific command-dir detection logic.

Poem

🐰 I hopped through code to add Insiders cheer,
Paths for each OS, now crystal clear,
Tests in place, docs shining bright,
Prompts kept separate, every platform right,
A tiny rabbit clap — well done, good night! ✨

Pre-merge checks

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'Feat/add vs code insiders' is concise and directly relates to the primary change: adding VS Code Insiders support. It clearly communicates the main objective despite being brief.
Description check	✅ Passed	The description covers the required template sections with Why and What Changed clearly stated, includes Testing details, and has a completed Checklist. However, Additional Notes section is missing and missing issue linkage.
Docstring Coverage	✅ Passed	Docstring coverage is 87.50% which is sufficient. The required threshold is 80.00%.

---

📜 Recent review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e215eae and 8f4f7a4.

📒 Files selected for processing (1)

• docs/specs/08-spec-vs-code-insiders-support/08-tasks-vs-code-insiders-support.md

✅ Files skipped from review due to trivial changes (1)

• docs/specs/08-spec-vs-code-insiders-support/08-tasks-vs-code-insiders-support.md

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI Agents

In
@docs/specs/08-spec-vs-code-insiders-support/08-tasks-vs-code-insiders-support.md:
- Line 21: Fix the concatenated text on line 21 in the doc string where
"introducedollow" appears; split and correct the sentence so it reads naturally
(for example: "introduced. Follow pytest parametrization patterns from existing
VS Code tests in `test_detection.py`"), ensuring proper spacing and punctuation
between the two clauses.

🧹 Nitpick comments (1)

docs/specs/08-spec-vs-code-insiders-support/08-spec-vs-code-insiders-support.md (1)

1-179: Excellent specification document with clear requirements and approach.

The specification is comprehensive, well-organized, and provides clear guidance for implementation. It covers all necessary aspects including goals, user stories, technical considerations, testing strategy, and success metrics. The approach to mirror existing VS Code support with Insiders-specific paths is sound and follows established patterns.

Optional: Minor style improvement for user stories

The static analysis tool noted that three consecutive user stories begin with "As a..." which can be slightly repetitive. While this follows the standard user story format and is not incorrect, you could optionally vary the sentence structure for improved readability. However, maintaining consistency with user story conventions is also valuable, so this is purely optional.

📜 Review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0ec4dc1 and e215eae.

📒 Files selected for processing (14)

• README.md
• docs/slash-command-generator.md
• docs/specs/08-spec-vs-code-insiders-support/08-proofs/08-task-01-proofs.md
• docs/specs/08-spec-vs-code-insiders-support/08-proofs/08-task-02-proofs.md
• docs/specs/08-spec-vs-code-insiders-support/08-proofs/08-task-03-proofs.md
• docs/specs/08-spec-vs-code-insiders-support/08-proofs/08-task-04-proofs.md
• docs/specs/08-spec-vs-code-insiders-support/08-questions-1-vs-code-insiders-support.md
• docs/specs/08-spec-vs-code-insiders-support/08-spec-vs-code-insiders-support.md
• docs/specs/08-spec-vs-code-insiders-support/08-tasks-vs-code-insiders-support.md
• docs/specs/08-spec-vs-code-insiders-support/08-validation-vs-code-insiders-support.md
• slash_commands/config.py
• tests/integration/test_generate_command.py
• tests/test_config.py
• tests/test_detection.py

🧰 Additional context used

📓 Path-based instructions (1)

slash_commands/**/*

📄 CodeRabbit inference engine (AGENTS.md)

Follow existing code patterns in slash_commands/

Files:

• slash_commands/config.py

🧬 Code graph analysis (1)

tests/test_detection.py (2)

slash_commands/detection.py (1)

• detect_agents (11-25)

slash_commands/config.py (2)

• get_agent_config (177-183)
• get_command_dir (35-43)

🪛 LanguageTool

docs/specs/08-spec-vs-code-insiders-support/08-questions-1-vs-code-insiders-support.md

[style] ~3-~3: Consider using a less common alternative to make your writing sound more unique and professional.
Context: ...r more options, or add your own notes). Feel free to add additional context under any questi...

(FEEL_FREE_TO_STYLE_ME)

---

[style] ~15-~15: ‘exact same’ might be wordy. Consider a shorter alternative.
Context: ... Additional context: Following the exact same cross-platform support as regular VS Co...

(EN_WORDINESS_PREMIUM_EXACT_SAME)

docs/specs/08-spec-vs-code-insiders-support/08-spec-vs-code-insiders-support.md

[style] ~21-~21: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...pt configurations without conflicts. As a cross-platform user, I want VS Code...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)

---

[style] ~23-~23: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...e regardless of my operating system. As a CLI user, I want VS Code Insiders t...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)

docs/specs/08-spec-vs-code-insiders-support/08-validation-vs-code-insiders-support.md

[style] ~164-~164: This phrase is redundant (‘OS’ stands for ‘operating system’). Use simply “macOS”.
Context: ...itioned after vs-code - ✅ Detected on macOS system (system has VS Code Insiders installed)...

(ACRONYM_TAUTOLOGY)

---

[uncategorized] ~236-~236: The official name of this software platform is spelled with a capital “H”.
Context: ...regressions in CLI, config, generators, github_utils, prompts, validation, version, or...

(GITHUB)

---

[grammar] ~327-~327: Use a hyphen to join words.
Context: ...iant (verified by passing tests) - ✅ 100 character line limit respected - ✅ Type ...

(QB_NEW_EN_HYPHEN)

🔇 Additional comments (13)

slash_commands/config.py (1)

80-96: LGTM! VS Code Insiders configuration follows the established pattern.

The new agent entry correctly mirrors the VS Code configuration with adjusted paths for the Insiders variant. All required fields are present with appropriate values:

• Platform-specific detection directories for all three platforms
• Platform-specific command directories matching VS Code Insiders installation paths
• Consistent file extension (.prompt.md) and format (CommandFormat.MARKDOWN)
• Proper key naming (vs-code-insiders) that maintains the existing naming convention

tests/integration/test_generate_command.py (1)

223-232: LGTM! VS Code Insiders correctly added to integration tests.

The agent is properly added in alphabetical order (after "vs-code") and will be validated through the existing test loop that verifies:

• Successful generation (exit code 0)
• Correct agent-specific directory creation
• File generation with proper extension

README.md (1)

195-198: LGTM! Clear and consistent documentation.

The VS Code Insiders entry is well-documented with platform-specific paths that correctly mirror the VS Code structure. The formatting is consistent with other platform-specific agents in the list.

tests/test_config.py (1)

115-119: LGTM! Test follows established pattern.

The test case for VS Code Insiders correctly mirrors the VS Code test pattern and validates the detection directory structure. The assertion properly checks for both the root .config directory and the specific .config/Code - Insiders path.

docs/specs/08-spec-vs-code-insiders-support/08-proofs/08-task-04-proofs.md (1)

1-105: Comprehensive proof artifacts.

This documentation provides thorough verification artifacts for Task 4.0, including code samples, verification checklists, and consistency reviews. The proof document clearly demonstrates that the documentation updates are complete and accurate.

docs/slash-command-generator.md (2)

198-198: LGTM! Table entry is complete and accurate.

The VS Code Insiders table entry correctly follows the established format with appropriate agent key, display name, format, extension, and reference links. The placement in alphabetical order after vs-code is correct.

---

201-215: Excellent documentation of platform-specific paths and independence.

The updated platform notes section clearly documents VS Code Insiders paths for all three platforms and explicitly states that VS Code and VS Code Insiders "operate independently" and "do not share configurations." This clarity is important to prevent user confusion about the relationship between the two variants.

docs/specs/08-spec-vs-code-insiders-support/08-proofs/08-task-01-proofs.md (1)

1-110: Thorough proof artifacts for configuration validation.

This documentation provides comprehensive validation for Task 1.0, including the configuration code structure, CLI output demonstrating agent discoverability, and test results confirming all configuration tests pass with no regressions. The proof artifacts clearly demonstrate that the VS Code Insiders configuration follows the correct pattern with platform-specific paths.

docs/specs/08-spec-vs-code-insiders-support/08-proofs/08-task-02-proofs.md (1)

1-161: Excellent documentation of test implementation and results.

The proof artifacts are thorough and well-organized. The documentation clearly shows:

• Test code implementation with proper parametrization
• Comprehensive test results (9 new tests, all passing)
• No regressions in existing tests
• Clear verification checklist

This provides strong evidence that the VS Code Insiders detection tests are properly implemented and validated.

tests/test_detection.py (3)

98-117: LGTM! Well-structured multiplatform detection test.

The test correctly validates VS Code Insiders detection across all three platforms using parametrization and monkeypatch. The platform-specific directory paths align with VS Code Insiders conventions, and the test structure mirrors the established pattern from the existing VS Code tests.

---

119-130: LGTM! Proper negative test case for detection.

The test correctly verifies that VS Code Insiders is not detected when its configuration directories don't exist. This negative test is important for ensuring accurate detection behavior and follows the established pattern from existing tests.

---

152-170: LGTM! Comprehensive test of platform-specific command directory resolution.

The test correctly validates that get_command_dir() returns the appropriate platform-specific path for VS Code Insiders, including the /User/prompts subdirectory. The test covers all three platforms and follows the established pattern from existing VS Code tests.

docs/specs/08-spec-vs-code-insiders-support/08-proofs/08-task-03-proofs.md (1)

1-117: Thorough documentation of integration test updates.

The proof artifacts clearly document the integration test changes, including:

• Addition of vs-code-insiders to the test agent list in proper alphabetical order
• Rationale for Docker isolation (preventing user data modification)
• Expected test behavior across platforms
• Comprehensive verification checklist

The documentation provides clear evidence that integration testing is properly configured for VS Code Insiders support.

[ryderstorm]

Thanks for knocking this out @m-schaller-3 !