Skip to content

fix(powershell): treat bracketed feature paths literally - #4970

Open
WOLIKIMCHENG wants to merge 1 commit into
github:mainfrom
WOLIKIMCHENG:fix/powershell-bracket-feature-paths
Open

WOLIKIMCHENG wants to merge 1 commit into
github:mainfrom
WOLIKIMCHENG:fix/powershell-bracket-feature-paths

Conversation

@WOLIKIMCHENG

@WOLIKIMCHENG WOLIKIMCHENG commented Oct 15, 2026 •

Copy link
Copy Markdown
Contributor

Description

PowerShell can treat square brackets in a feature directory name as wildcards, causing task setup or prerequisite checks to miss existing files or match a neighboring directory.

  • Use literal-path checks and directory enumeration for feature-derived paths.
  • Add regression coverage for bracketed paths and wildcard-shaped neighbors.

Testing

  • Focused Python tests: 64 passed.
  • Windows PowerShell 5.1: the bracket-path case failed before this change and passed after it; the neighboring-directory case was correctly rejected.
  • Sample project: specify, plan, tasks, checklist, and analyze workflows completed with a bracketed feature directory.
  • git diff --check passed.

AI Disclosure

  • I did use AI assistance (described below)

AI disclosure: AI-assisted tools were used to implement the fix and develop tests.

Assisted-by: Codex CLI (model: gpt-5.6-terra, autonomous)
@WOLIKIMCHENG
WOLIKIMCHENG requested a review from mnriem as a code owner October 15, 2026 08:52

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant