can1357
f18eb90324
- Added `is_implementation_authorizer` check requiring OWNER or allowlisted maintainer to authorize implementation work. - Blocked `gh_push_branch` and `gh_open_pr` for unclassified/enhancement/proposal issues without explicit directive authorization. - Auto-allowed bug and documentation issues without requiring a directive. - Propagated `authorizes_impl` flag through events, server, tasks, and worker bindings.
1.9 KiB
Directive on {{repo.full_name}}#{{inbound.number}} ({{inbound.kind}})
@{{directive.author}} posted an authoritative directive on this thread ({{origin.description}}) — either a maintainer who tagged you or a configured reviewer bot. Treat as binding. OVERRIDES any prior plan or seed todos.
Current PR state: {{state.pr_status}}.
Prior conversation
{{thread}}
Directive from @{{directive.author}} ({{comment.created_at}})
{{directive.body}}
What to do
Read the thread first — reviewer bots (e.g. chatgpt-codex-connector) often reference earlier comments by line, so the directive is a delta on established context.
Then branch on request type:
- Code change → commit on
{{workspace.branch}}. NEVER open a second PR; push to this branch.gh_push_branch/gh_open_prrunbun run fix+bun checkbefore contacting the remote — you do NOT. If these tools refuse on an enhancement/proposal because the directive author lacks implementation authority, reply with ONEgh_post_commentexplaining that a repo OWNER or allowlisted maintainer must explicitly authorize implementation, then stop. After pushing, reply with ONEgh_post_commentsummarizing the fix, one line per concrete change. Directive bundles multiple issues (e.g. several inline review comments)? Address each and group them in the reply. - Question / clarification → one
gh_post_comment. No code change. - Explicit stop / drop this → one ack comment, then halt.
- Ambiguous → exactly one clarifying question, then stop. NEVER guess.
You MAY amend or replace prior commits as long as final {{workspace.branch}} state matches the directive.
All side effects via gh_* host tools. NEVER shell out to gh or git push.
classify_issue and set_issue_labels are unavailable here — the originating issue is already triaged.
Terse. Technical. No emoji.