python-policy

Enforce Python changes to follow checked-in tooling and bootstrap rules.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/hack-ink/codexlab --skill python-policy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: python-policy
Source: https://github.com/hack-ink/codexlab/tree/main/.codex/skills/python-policy
Command: npx skills add https://github.com/hack-ink/codexlab --skill python-policy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This policy document ensures Python changes align with the repository's checked-in tooling and bootstrap rules, rather than personal defaults.

Core Features & Use Cases

  • Defines authoritative tooling and runtime guidance to govern Python work across services, libraries, and tooling within hack-ink repositories.
  • Promotes adherence to the touched project's checked-in bootstrap paths and project-configured environments for consistency and reproducibility.
  • Provides guardrails for environment management, dependency handling, and CI workflows to minimize drift.

Quick Start

Consult this policy before modifying Python code to ensure your changes follow the project's configured tooling and bootstrap rules.

Frequently Asked Questions about python-policy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce Python runtime safety in a CI workflow?

Enforce Python runtime safety by aligning code changes with the project's checked-in tooling and bootstrap path, using documented config and CI commands to minimize environment drift.

What is a Python bootstrap path and when do I need it?

A Python bootstrap path is the project's authoritative runtime selection and tooling setup mechanism. You need it when modifying Python services, libraries, or tooling to ensure reproducible environments.

Why does my Python CI pipeline fail due to personal environment drift?

Python CI pipelines fail from environment drift when changes rely on personal defaults instead of the project's checked-in tooling. Following the repository's bootstrap rules and project-configured environments prevents this.

How to manage Python project-configured environments for consistent builds?

Manage Python project-configured environments by following the repository's checked-in bootstrap paths and documented CI commands, avoiding personal environment changes to maintain build consistency.

Does this Python policy apply to all Python services and libraries?

Yes, this Python policy applies to Python services, libraries, and tooling within hack-ink repositories whenever Python code or tooling is touched, governing environment management and dependency handling.

Can I use my local Python runtime instead of the project's checked-in tooling?

No, you should not use personal local runtimes. The policy requires following the project's bootstrap and runtime selection rules to ensure changes align with checked-in tooling for reproducibility.