feat(scripts): add dynamic Python skill discovery for lint/test

[JasonOA888]

Implements dynamic discovery of Python skills by finding all pyproject.toml files and running ruff/pytest on each.

Motivation

As the project grows to support more Python skills, we need a way to automatically discover and lint/test all of them without manually updating npm scripts.

Changes

New Scripts

scripts/linting/
├── Invoke-PythonLint.ps1    # Discovers Python skills, runs ruff
└── Invoke-PythonTests.ps1   # Discovers Python skills, runs pytest

How It Works

1. Scans repository for pyproject.toml files (excludes node_modules)
2. For each Python skill:
   • lint:py runs ruff check
   • test:py runs pytest (if tests/ directory exists)
3. Reports summary of passed/failed skills

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

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

Benefits

• Automatic discovery: New Python skills are automatically included
• Cross-platform: PowerShell scripts work on Windows/Linux/macOS
• Clear output: Shows which skills passed/failed
• Fail-fast: Returns non-zero exit code on any failure

Testing

• Tested with multiple pyproject.toml files
• Handles missing ruff/pytest gracefully
• Excludes node_modules correctly

Addresses feedback from #933

Closes #933

[WilliamBerryiii]

Hey @JasonOA888 — thanks for tackling #933! A few things I wanted to call out that the review comments don't fully capture:

What this PR does well:

• The pyproject.toml discovery pattern is exactly the right approach. It mirrors how CI and the devcontainer already locate Python skills, so new skills get picked up automatically without manual script updates.
• The structured output with pass/fail summaries and emoji indicators makes it easy to scan results at a glance.
• The Push-Location / Pop-Location / finally pattern (intent-wise) is the correct way to handle directory changes safely in PowerShell.
• Error handling with exit codes is clean and CI-friendly.

Quick orientation for the convention items:
The review has several "align with sibling scripts" comments. The easiest way to address all of them at once is to use Invoke-PSScriptAnalyzer.ps1 as your template — it has the full pattern with copyright header, CmdletBinding, params, region blocks, shared module imports, and the main execution guard. Invoke-YamlLint.ps1 is another good reference with a simpler structure.

On the uv vs pip item:
This one might not be obvious if you haven't seen the CI configuration. The project uses uv (by Astral, the same team behind ruff) for Python environment management. Both copilot-setup-steps.yml and the devcontainer's on-create.sh run find .github/skills -name pyproject.toml -execdir uv sync \; to pre-install dependencies. So by the time these scripts run, ruff and pytest should already be available through each skill's pyproject.toml. The auto-install fallback is a nice thought, but pip can conflict with uv-managed environments.

Let me know if any of the review feedback is unclear — happy to pair on the changes or answer questions. Looking forward to the next iteration! 🚀

Dismissing my own review and passing to a peer because of the extra changes

[codecov-commenter]

Codecov Report

❌ Patch coverage is 86.61972% with 19 lines in your changes missing coverage. Please review.
✅ Project coverage is 86.03%. Comparing base (f4deda7) to head (9da47fd).
⚠️ Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
scripts/linting/Invoke-PythonTests.ps1	81.81%	12 Missing ⚠️
scripts/linting/Invoke-PythonLint.ps1	87.03%	7 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #957      +/-   ##
==========================================
+ Coverage   86.01%   86.03%   +0.01%     
==========================================
  Files          28       30       +2     
  Lines        5270     5412     +142     
==========================================
+ Hits         4533     4656     +123     
- Misses        737      756      +19     

Flag	Coverage Δ
pester	86.03% <86.61%> (+0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
scripts/linting/Validate-SkillStructure.ps1	96.00% <100.00%> (+0.43%)	⬆️
scripts/linting/Invoke-PythonLint.ps1	87.03% <87.03%> (ø)
scripts/linting/Invoke-PythonTests.ps1	81.81% <81.81%> (ø)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[WilliamBerryiii]

Hey @JasonOA888 — huge thank you for putting this together! 🎉

The dynamic Python skill discovery is exactly the kind of infrastructure improvement that pays dividends as the project grows. Really appreciate the thoughtfulness here: automatic pyproject.toml scanning, clean summary output, graceful handling of missing tools, and solid cross-platform support. The attention to detail shows.

We took it from here and got it merged. Your contribution makes life easier for everyone adding Python skills going forward.

Thanks again for the time and effort — looking forward to more contributions from you! 🙌