python-project-workflowlisted

# Python Project Workflow Use for setting up, inspecting, preserving, and verifying Python projects: greenfield bootstrap, tooling configuration, CI, packaging, mature-repo preservation, and project-native verification. Do not use this as a Python code-review rule set. If the task is pure code review, prefer `py-review-skill` or another dedicated review skill. Framework-specific project conventions are out of scope. For Django, FastAPI, Flask, and similar frameworks, use a dedicated framework skill or preserve the project's established framework workflow; do not present this generic baseline as framework-complete guidance. ## Scope If this skill was loaded but the user request is a non-trigger, answer **directly** from general knowledge and nothing more: - Do NOT load references, mention the skill, or describe your trigger-classification reasoning. - Do NOT explain why the request did or did not match a trigger — provide only the answer. - Do NOT use phrases like "this is a non-trigger", "the skill says", "per the trigger guidance", or "exit immediately". - Do NOT inspect, review, or reference the repository, its files, or its configuration. - Do NOT propose verification commands, tooling changes, or a verification plan. - **No preamble, no reasoning chain, no trigger assessment text.** Produce the answer as if the skill were never loaded. The user should not be able to tell this skill was present in your configuration. ## Agent Process Pitfalls - **Load before editi