Add follow-up issue guidance
This commit is contained in:
@@ -20,6 +20,7 @@ Preserve unrelated user changes.
|
||||
Replace all applicable placeholders and remove non-applicable placeholder sections.
|
||||
Keep AGENTS.md and .codex/project.md aligned with real commands and artifact paths.
|
||||
Update README.md whenever blueprint.md or blueprint.json changes.
|
||||
Create tracker issues for real, actionable follow-ups that are outside the current scope or independently parallelizable; use docs/agent-handoff.md when no issue tracker is available.
|
||||
Exclude Codex kit metadata from user-facing release, package, installer, archive, and GitHub/Gitea upload artifacts unless explicitly requested.
|
||||
Run git diff --check before finishing.
|
||||
Run the cheapest reliable verification command, or explain why it could not run.
|
||||
@@ -137,6 +138,14 @@ Is the work interrupted, risky, or multi-session?
|
||||
yes -> update docs/agent-handoff.md
|
||||
no -> no handoff file is required
|
||||
|
||||
Did you find real follow-up work outside the current scope?
|
||||
yes -> create focused tracker issues for independent work; include impact, affected files, next steps, and verification
|
||||
no -> do not create placeholder issues
|
||||
|
||||
Could the issue expose secrets, private data, or sensitive logs?
|
||||
yes -> do not put sensitive details in a public issue; summarize safely and keep details private or in handoff notes
|
||||
no -> continue
|
||||
|
||||
Is this a private Gitea repo with Actions?
|
||||
yes -> if GITEA_TOKEN is set locally, use it for read-only API checks of repository and workflow-run status
|
||||
no -> use public web/API checks when available
|
||||
|
||||
Reference in New Issue
Block a user