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!

PR Compliance Update — The following adjustments were made to align this PR with project conventions:

1. Title scope: Changed feat(ci): → feat(workflows): — the project uses workflows as the conventional scope for CI/workflow file changes (see .github/instructions/hve-core/commit-message.instructions.md).
2. PR body: 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 #890 reference were preserved.

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

@JasonOA888 please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.

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

Options:

• (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

• (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

@microsoft-github-policy-service agree company="Microsoft"

Contributor License Agreement

Contribution License Agreement

This Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”), and conveys certain license rights to Microsoft Corporation and its affiliates (“Microsoft”) for Your contributions to Microsoft open source projects. This Agreement is effective as of the latest signature date below.

1. Definitions.
   “Code” means the computer software code, whether in human-readable or machine-executable form,
   that is delivered by You to Microsoft under this Agreement.
   “Project” means any of the projects owned or managed by Microsoft and offered under a license
   approved by the Open Source Initiative (www.opensource.org).
   “Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any
   Project, including but not limited to communication on electronic mailing lists, source code control
   systems, and issue tracking systems that are managed by, or on behalf of, the Project for the purpose of
   discussing and improving that Project, but excluding communication that is conspicuously marked or
   otherwise designated in writing by You as “Not a Submission.”
   “Submission” means the Code and any other copyrightable material Submitted by You, including any
   associated comments and documentation.
2. Your Submission. You must agree to the terms of this Agreement before making a Submission to any
   Project. This Agreement covers any and all Submissions that You, now or in the future (except as
   described in Section 4 below), Submit to any Project.
3. Originality of Work. You represent that each of Your Submissions is entirely Your original work.
   Should You wish to Submit materials that are not Your original work, You may Submit them separately
   to the Project if You (a) retain all copyright and license information that was in the materials as You
   received them, (b) in the description accompanying Your Submission, include the phrase “Submission
   containing materials of a third party:” followed by the names of the third party and any licenses or other
   restrictions of which You are aware, and (c) follow any other instructions in the Project’s written
   guidelines concerning Submissions.
4. Your Employer. References to “employer” in this Agreement include Your employer or anyone else
   for whom You are acting in making Your Submission, e.g. as a contractor, vendor, or agent. If Your
   Submission is made in the course of Your work for an employer or Your employer has intellectual
   property rights in Your Submission by contract or applicable law, You must secure permission from Your
   employer to make the Submission before signing this Agreement. In that case, the term “You” in this
   Agreement will refer to You and the employer collectively. If You change employers in the future and
   desire to Submit additional Submissions for the new employer, then You agree to sign a new Agreement
   and secure permission from the new employer before Submitting those Submissions.
5. Licenses.

• Copyright License. You grant Microsoft, and those who receive the Submission directly or
  indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license in the
  Submission to reproduce, prepare derivative works of, publicly display, publicly perform, and distribute
  the Submission and such derivative works, and to sublicense any or all of the foregoing rights to third
  parties.
• Patent License. You grant Microsoft, and those who receive the Submission directly or
  indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license under
  Your patent claims that are necessarily infringed by the Submission or the combination of the
  Submission with the Project to which it was Submitted to make, have made, use, offer to sell, sell and
  import or otherwise dispose of the Submission alone or with the Project.
• Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement.
  No additional licenses or rights whatsoever (including, without limitation, any implied licenses) are
  granted by implication, exhaustion, estoppel or otherwise.

6. Representations and Warranties. You represent that You are legally entitled to grant the above
   licenses. You represent that each of Your Submissions is entirely Your original work (except as You may
   have disclosed under Section 3). You represent that You have secured permission from Your employer to
   make the Submission in cases where Your Submission is made in the course of Your work for Your
   employer or Your employer has intellectual property rights in Your Submission by contract or applicable
   law. If You are signing this Agreement on behalf of Your employer, You represent and warrant that You
   have the necessary authority to bind the listed employer to the obligations contained in this Agreement.
   You are not expected to provide support for Your Submission, unless You choose to do so. UNLESS
   REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, AND EXCEPT FOR THE WARRANTIES
   EXPRESSLY STATED IN SECTIONS 3, 4, AND 6, THE SUBMISSION PROVIDED UNDER THIS AGREEMENT IS
   PROVIDED WITHOUT WARRANTY OF ANY KIND, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY OF
   NONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
7. Notice to Microsoft. You agree to notify Microsoft in writing of any facts or circumstances of which
   You later become aware that would make Your representations in this Agreement inaccurate in any
   respect.
8. Information about Submissions. You agree that contributions to Projects and information about
   contributions may be maintained indefinitely and disclosed publicly, including Your name and other
   information that You submit with Your Submission.
9. Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and
   the parties consent to exclusive jurisdiction and venue in the federal courts sitting in King County,
   Washington, unless no federal subject matter jurisdiction exists, in which case the parties consent to
   exclusive jurisdiction and venue in the Superior Court of King County, Washington. The parties waive all
   defenses of lack of personal jurisdiction and forum non-conveniens.
10. Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and
    supersedes any and all prior agreements, understandings or communications, written or oral, between
    the parties relating to the subject matter hereof. This Agreement may be assigned by Microsoft.

@microsoft-github-policy-service agree

@microsoft-github-policy-service agree

Thanks for the detailed review @katriendg! The feedback is very helpful.

I can see the PR is missing several key requirements from #890:

1. ❌ working-directory input for multi-skill support
2. ❌ uv sync --locked instead of uv pip install --system
3. ❌ pr-validation.yml integration
4. ❌ codecov.yml flag configuration
5. ❌ pytest-mock in skill dev dependencies
6. ❌ uv run pytest instead of bare pytest
7. ❌ Remove code-coverage toggle

I'd like to update this PR to address all the requirements. A few clarifying questions:

1. Should I also update the PowerPoint skill's pyproject.toml to add pytest-mock, or is that a separate PR?
2. For the orchestrator integration, should each Python skill get its own job entry in pr-validation.yml, or should there be a matrix strategy?

I'll start working on the updates.

PR updated to address all review feedback:

Changes Made

1. pytest-tests.yml (new reusable workflow)

• ✅ Added working-directory input for multi-skill support
• ✅ Uses uv sync --locked for dependency management (not uv pip install --system)
• ✅ Runs uv run pytest within skill's virtual environment
• ✅ Always collects coverage (removed code-coverage toggle)
• ✅ Uploads to Codecov with pytest flag

2. pr-validation.yml

• ✅ Added pytest-powerpoint job that calls the new workflow
• ✅ Uses working-directory: .github/skills/experimental/powerpoint
• ✅ Set changed-files-only: true to skip if no Python changes

3. codecov.yml

• ✅ Added pytest coverage flag with path filter .github/skills/**/scripts/**
• ✅ Enabled carryforward: true

Notes

• pytest-mock in skill dev dependencies: This requires modifying each skill's pyproject.toml. Since the PowerPoint skill PR (feat(skills): add PowerPoint automation skill with YAML-driven deck generation #868) is still pending, I haven't modified any skill files. Once a Python skill is merged, its pyproject.toml should include pytest-mock>=3.14 in [dependency-groups] dev.

• Multiple skills: Adding new Python skills requires only a new job entry in pr-validation.yml calling the reusable workflow with the appropriate working-directory.

@JasonOA888, thank you for the quick turnaround addressing the earlier feedback. The reusable workflow (pytest-tests.yml) itself is well-structured: working-directory input, uv sync --locked, uv run pytest, Codecov OIDC upload with the pytest flag, and the changed-files-only skip logic are all solid. Appreciate the effort here.

Two items remain before this can move forward:

1. Discovery instead of hardcoding. The pytest-powerpoint job in pr-validation.yml hardcodes a single skill directory. The project convention (see extension-package.yml discover-collections) is to dynamically discover targets. For pytest, this means a discovery job that finds all pyproject.toml files under .github/skills/ and emits their parent directories as a JSON matrix, with a downstream matrix job calling pytest-tests.yml per skill. This way, adding a new Python skill only requires dropping a pyproject.toml in the skill folder with no workflow edits.

2. Dependency on PR feat(skills): add PowerPoint automation skill with YAML-driven deck generation #868. This PR targets a skill directory that doesn't exist on main yet (the PowerPoint skill lands with feat(skills): add PowerPoint automation skill with YAML-driven deck generation #868). Without that, there's nothing for this workflow to discover or test against.

I'd recommend converting this PR to draft until #868 merges, then rebasing and reworking the pr-validation.yml integration with the discovery pattern. That gives us a real end-to-end validation path.
@WilliamBerryiii agree?

The contribution is valuable and aligns well with the #890 requirements. Once #868 is in, we can get this across the finish line quickly. Thanks again!

Updated to use dynamic discovery following project conventions.

Changes

1. Discovery Job (discover-python-skills)

• Finds all pyproject.toml files under .github/skills/
• Builds JSON matrix with skill name and working directory
• Outputs has-skills flag to skip if no Python skills found

2. Matrix-based pytest Job

• Replaces hardcoded pytest-powerpoint job
• Uses fromJson(needs.discover-python-skills.outputs.matrix)
• Each skill runs independently with fail-fast: false

3. Result

Adding a new Python skill now only requires:

1. Create skill folder under .github/skills/
2. Add pyproject.toml with [dependency-groups] dev = ["pytest>=8.0", "ruff>=0.4", "pytest-mock>=3.14"]
3. No workflow edits needed

Note on PowerPoint Skill (#868)

The workflow will pass with an empty matrix until the PowerPoint skill lands. Once #868 merges, the discovery job will automatically find it.

This follows the same pattern as extension-package.yml discover-collections.

@katriendg Sounds good! I'll keep this PR ready and rebased.

Once #868 merges, I'll:

1. Rebase onto main
2. Verify discovery finds the PowerPoint skill
3. Confirm end-to-end test execution

The workflow is already structured for dynamic discovery, so it should work automatically once a Python skill exists in the repo.

(Unable to convert to draft via API, but consider this ready-and-waiting)

Hey @JasonOA888 — just wanted to take a moment to say thank you for picking up these backlog items and driving them forward. Adding Python testing CI with pytest and Codecov integration is a meaningful contribution to the project, and the dynamic skill discovery via matrix strategy is a great pattern that will scale well as more Python skills are added.

We really appreciate your patience working through the review feedback and revisions with us — the PR has shaped up well through the collaboration. The workflow is solid, the coverage configuration is clean, and the overall design fits nicely into the existing CI architecture.

I've pushed a few additional commits to the branch to address the remaining review items and CI issues we identified together:

• Test coverage: Rewrote test_validate_slides.py to match the current module interface (post-PR feat(skills): add PowerPoint automation skill with YAML-driven deck generation #868 merge), and added comprehensive tests for build_deck.main() and render_pdf_images — bringing overall coverage to 90% with all scripts above the 80% threshold
• CI fixes: Updated pinned SHAs for astral-sh/setup-uv (v7.4.0) and actions/setup-python (v6.2.0), and sanitized the upload-artifact name to handle forward slashes in the working directory path
• Code quality: Cleaned up unused imports flagged by CodeQL

Thanks again for the contribution — looking forward to getting this merged! 🚀