Skip to content

docs(skill): invoke PowerShell wrapper with call operator - #26

Merged
Nikita Kuchur (nikitakuchur) merged 1 commit into
JetBrains:mainfrom
FenjuFu:fix/powershell-call-operator
Aug 30, 2026
Merged

Nikita Kuchur (nikitakuchur) merged 1 commit into
JetBrains:mainfrom
FenjuFu:fix/powershell-call-operator

Conversation

@FenjuFu

Copy link
Copy Markdown
Contributor

Summary

Prefix the documented Windows PowerShell wrapper path with the call operator (&) so PowerShell executes the script instead of parsing the path as a string literal.

Reproduction

Applied the skill to harnessclaw/harnessclaw-engine, the Go repository in the iflytek-astron topic (go 1.26.1):

  • documented command without &: PowerShell exits with ParserError / UnexpectedToken at the list argument;
  • corrected command with &: wrapper exits 0, installs/executes v0.1.1, detects the target file's Go version, and returns the applicable guideline list.

Validation

  • go test ./internal/cli ./internal/goversion ./internal/guidelines ./internal/guidelines/schema — pass
  • go test ./... — all packages pass except the existing CRLF-sensitive TestFeaturesMarkdownInSync on this Windows checkout; this PR does not modify FEATURES.md, the generator, or guideline data
  • git diff --check — pass

Closes #25.

@nikitakuchur
Nikita Kuchur (nikitakuchur) merged commit ae41af9 into JetBrains:main Aug 30, 2026
@nikitakuchur

Copy link
Copy Markdown
Collaborator

Thank you for the fix!

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.

SKILL.md: Windows PowerShell invocation is a bare string literal; needs the call operator (&)

2 participants