Files

T

malkuthroandClaude Opus 4.7 b42bd4af77 chore(python): add bootstrap scripts + pip-audit + line-ending policy (#158 )

Solidify the Python test-env path so any agent (Claude / Codex) or
human can bootstrap with one command, and so the global preflight
skill's pip-audit branch actually runs against this repo.

scripts/bootstrap_test_env.{ps1,sh}: one-liner per platform, idempotent
  (no-op if .venv exists, --force / -Force to recreate), upgrades pip,
  installs project + test extras.

pyproject.toml: add pip-audit>=2.7 to [project.optional-dependencies]
  test so /preflight's Python audit branch lights up.

CLAUDE.md, Hard rules: replace the inline venv-bootstrap command with
  a reference to the platform script.

AGENTS.md: short "Test Environment Bootstrap" pointer (mirrors CLAUDE.md
  per the Claude/Codex symmetry rule).

.gitattributes: enforce LF for *.sh (otherwise Windows CRLF breaks the
  bash shebang on POSIX) and CRLF for *.ps1 (Windows convention).

Triggered by the warmup-skill Python detection added in agent-playbooks
PR #34 — projects now need a clean bootstrap path for the new check to
have a recommended remediation.

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-05-17 21:19:20 +02:00

1.8 KiB

Raw Blame History

ComfyUI-Koolook Codex Instructions

Required Project Context

Read CLAUDE.md before making substantive changes. It contains the project-specific workflow, dev-sync rules, release rules, and sidebar maintenance notes.

Test Environment Bootstrap

Use scripts\bootstrap_test_env.ps1 (Windows) or bash scripts/bootstrap_test_env.sh (POSIX) to create .venv and install test deps. Never install into system Python. Full rule in CLAUDE.md § Hard rules.

External Repository Boundary

If a user request appears to involve files, workflows, repositories, or publishing targets that are not present in this repository, stop and confirm the exact target before acting. Dictation typos and shorthand are common; do not infer a sibling repository or revive old local workflows from broad filesystem search results without explicit user confirmation.

Visual QA Is Mandatory For UI Work

For any change that affects rendered UI, guide pages, screenshots, CSS/layout, onboarding docs, or browser-visible behavior:

Do not rely on CSS coordinates, source inspection, or user screenshots alone.
Open the changed page/app in a browser-rendered environment that Codex can screenshot.
If a file:// guide page is blocked by browser tooling, serve the repo over local HTTP instead, for example: python3 -m http.server <port> from the repo root, then open http://127.0.0.1:<port>/....
Take a rendered screenshot after the change and inspect the actual visual result before committing or pushing.
If visual verification is blocked, say that clearly and do not present the UI change as ready unless the user explicitly waives visual QA.

This is especially important for overlays, icon highlights, responsive layout, text fitting, and visual guide pages.