prlisted

# PR Create or update a GitHub PR with a clear title/body, then immediately hand it to my-calendar's `pr-created` hook so Codex review runs asynchronously and writes the result into the "PR 监控" calendar. This is the light path. Do not run the full `/ship` ceremony: no version bump, no CHANGELOG, no TODOS sweep, no review army, no release promotion. ## Workflow 1. Preflight the repo. ```bash git rev-parse --show-toplevel git branch --show-current git remote get-url origin git status --short gh auth status ``` Abort if the current branch is the PR base/default branch, if the remote is not GitHub, or if `gh` is not authenticated. 2. Understand the diff and run a narrow verification. Use the repository's existing instructions first (`AGENTS.md`, `README`, package scripts, Makefile, CI config). Prefer the smallest check that reasonably covers the changed surface. Do not invent a release checklist. If no obvious check exists, say that and continue only if the change is documentation/config-only or the user explicitly asked for a quick PR. 3. Commit local changes if needed. Stage files deliberately. Do not use `git add -A` unless the repository explicitly allows it and the status is clean of generated/local files. Preserve any unrelated user changes. Follow the repo's commit style. If the commit is AI-authored and the repo has an AI coauthor convention, include the appropriate trailer. 4. Prepare the PR title and description. Alwa