feat(scripts): add npm run scripts for Python linting and testing

[JasonOA888]

Description

Add npm run scripts for Python linting and testing:

• lint:py — ruff check
• lint:py:fix — ruff check --fix
• test:py — pytest

Follows existing npm script patterns.

Related Issue(s)

Fixes #886

Type of Change

Select all that apply:

Code & Documentation:

• Bug fix (non-breaking change fixing an issue)
• New feature (non-breaking change adding functionality)
• Breaking change (fix or feature causing existing functionality to change)
• Documentation update

Infrastructure & Configuration:

• GitHub Actions workflow
• Linting configuration (markdown, PowerShell, etc.)
• Security configuration
• DevContainer configuration
• Dependency update

AI Artifacts:

• Reviewed contribution with prompt-builder agent and addressed all feedback
• Copilot instructions (.github/instructions/*.instructions.md)
• Copilot prompt (.github/prompts/*.prompt.md)
• Copilot agent (.github/agents/*.agent.md)
• Copilot skill (.github/skills/*/SKILL.md)

Note for AI Artifact Contributors:

• Agents: Research, indexing/referencing other project (using standard VS Code GitHub Copilot/MCP tools), planning, and general implementation agents likely already exist. Review .github/agents/ before creating new ones.
• Skills: Must include both bash and PowerShell scripts. See Skills.
• Model Versions: Only contributions targeting the latest Anthropic and OpenAI models will be accepted. Older model versions (e.g., GPT-3.5, Claude 3) will be rejected.
• See Agents Not Accepted and Model Version Requirements.

Other:

• Script/automation (.ps1, .sh, .py)
• Other (please describe):

Testing

Checklist

Required Checks

• Documentation is updated (if applicable)
• Files follow existing naming conventions
• Changes are backwards compatible (if applicable)
• Tests added for new functionality (if applicable)

Required Automated Checks

The following validation commands must pass before merging:

• Markdown linting: npm run lint:md
• Spell checking: npm run spell-check
• Frontmatter validation: npm run lint:frontmatter
• Skill structure validation: npm run validate:skills
• Link validation: npm run lint:md-links
• PowerShell analysis: npm run lint:ps

[WilliamBerryiii]

Hi @JasonOA888 — thank you for taking the time to contribute to this project! We really appreciate the effort you've put into this PR.

Before we can review and merge your changes, we need you to sign the Microsoft Contributor License Agreement (CLA). The CLA bot should have posted instructions on this PR when it was opened. You can sign by posting the following comment:

@microsoft-github-policy-service agree

If you're contributing on behalf of a company, use:

@microsoft-github-policy-service agree company="{your company}"

We'd love to include your work, but unfortunately we won't be able to accept the contribution without a signed CLA. If we don't hear back, we'll eventually need to close this PR and potentially redo the work under a signed agreement.

Thanks again, and please let us know if you have any questions!

[WilliamBerryiii]

PR Compliance Update — The PR body was reformatted to use the project's PR template with all required sections (Related Issue(s), Type of Change, Checklist, Security Considerations, etc.). The original description and Fixes #886 reference were preserved.

No content was changed — only formatting alignment. Thank you for the contribution! 🙏

[katriendg]

@JasonOA888 thanks for taking the time for creating a contribution.
We noticed there are a few small things missing to align the change with the issue description: primarily each of these new additions should ensure dynamic discovery of each Skill using Python through their pyproject.yaml files, using find. Could you update your PR to match the issue requirements?

Thanks for the alphabetical ordering, this is helpful too!

[JasonOA888]

@microsoft-github-policy-service agree

[JasonOA888]

Thanks for the review @katriendg and @WilliamBerryiii!

The CLA has been signed.

Regarding the dynamic discovery of Python Skills using find - could you clarify what you'd like to see? The current PR adds simple npm scripts for Python linting/testing:

• lint:py → ruff check .
• test:py → pytest

Are you asking for these commands to dynamically discover Python files rather than running on .? Or is this about discovering Skills that use Python from their pyproject.yaml files?

Happy to update the PR once I understand the requirements better.

[WilliamBerryiii]

Thanks for the review @katriendg and @WilliamBerryiii!

The CLA has been signed.

Regarding the dynamic discovery of Python Skills using find - could you clarify what you'd like to see? The current PR adds simple npm scripts for Python linting/testing:

• lint:py → ruff check .
• test:py → pytest

Are you asking for these commands to dynamically discover Python files rather than running on .? Or is this about discovering Skills that use Python from their pyproject.yaml files?

Happy to update the PR once I understand the requirements better.

@JasonOA888 I'll get you an example in a min ... basically getting ruff mapped into all the various skills folders that have python in them. Obviously, right now we only have 1 skill still in PR form with python code in it, but we are anticipating needed to support a TON of skills where python is the backing code for the skill ... so we want to make sure the CLI commands for devs, go and find all the skills that py project toml files and lints them all. (Hope that clears things up)

[JasonOA888]

Thanks for the clarification @WilliamBerryiii!

I've created a new PR that implements dynamic discovery of Python skills:

PR: #935

Implementation

The new approach:

1. Scans for pyproject.toml files (excludes node_modules)
2. Runs ruff/pytest in each discovered directory
3. Reports summary of passed/failed skills

Scripts Added

scripts/linting/
├── Invoke-PythonLint.ps1    # Dynamic ruff linting
└── Invoke-PythonTests.ps1   # Dynamic pytest testing

Example Output

Found 3 Python skill(s):
  - ./skills/my-python-skill
  - ./skills/another-skill
  
Running ruff in ./skills/my-python-skill...
✓ No linting issues

Running ruff in ./skills/another-skill...
❌ Linting issues found

❌ Linting completed with errors

package.json Updates

{
  "lint:py": "pwsh -NoProfile -File ./scripts/linting/Invoke-PythonLint.ps1",
  "test:py": "pwsh -NoProfile -File ./scripts/linting/Invoke-PythonTests.ps1"
}

This design will automatically discover and lint/test ALL Python skills as they're added, without needing to update the npm scripts.

Closing this PR in favor of #935.

[WilliamBerryiii]

Ref #957 as the replacement! Closing this one