Thanks for improving Python Project Workflow. Only
skills/python-project-workflow/ ships to users; repository docs, fixtures,
scripts, CI, and root references/ are maintainer infrastructure.
- Read
skills/python-project-workflow/SKILL.mdand the relevant canonical file underreferences/. - Edit
SKILL.mdin place. Edit reference content only in rootreferences/, then runbash scripts/sync-payload.shto refresh the shipped mirror. - Keep frontmatter limited to
nameanddescription, keep the payload client-neutral, and preserve progressive disclosure. - Do not include credentials, private repository content, raw commit bodies, or secret-bearing URLs in fixtures, logs, commits, or reports.
Run the complete command list in the README's Verify section. The live
Codex and Hermes runners are intentionally optional because they require local
client access and may consume a subscription. Their --self-test modes are
deterministic and remain part of normal validation.
Live runners delete temporary fixtures by default; pass --retain-fixtures
only when debugging. The Hermes runner also refuses to start unless the payload
under the active HERMES_HOME exactly matches this repository, preventing stale
installations from producing runtime evidence.
When a change materially affects SKILL.md, an evaluation prompt, fixture,
schema, or grader, reset affected runtime claims to candidate. Promote a
runtime only with evidence that meets docs/portability-contract.md; a working
documentation link or structurally valid payload is not runtime verification.
Explain the user-visible behavior, list validation performed, and identify any runtime evidence that was reset, added, or intentionally left unverified. Keep generated evaluation artifacts out of Git; record only redacted summaries in maintainer documentation.
For releases, follow docs/release-checklist.md.