feat: api-derived commit subjects when PR_BODY is empty #37

Merged

joshtronic merged 1 commit from feat/api-derived-commit-subject into master

2026-05-19 03:19:31 +00:00

joshtronic commented

2026-05-19 03:18:56 +00:00

Owner

New tier-2 fallback: API-direct call to Haiku with the diff,
asking for a one-line conventional-commit subject. Single-shot,
no tool use, ~$0.005 per call, ~1-2s latency. Only fires when
PR_BODY.md is missing or empty -- when Claude writes a good
first item, that's still preferred (free, semantic, in his
voice).

New helper claude_complete does the API call generically:
curl POST /v1/messages, returns text. Reusable for future
in-harness thinking tasks (classification, summarization, etc.).
Model defaults to Haiku via new optional IGOR_MODEL_THINKING
env var; documented in .env.example.

Three-tier subject derivation now:

PR_BODY.md first "What this PR does" item -- preferred
API-generated from diff -- when PR_BODY misses
Hardcoded fallback -- when API also fails

Both tier-1 and tier-3 call sites updated to pass worktree path
so the diff is accessible to the API tier.

Generic fallback subjects ("chore: discretionary website tick") were unhelpful in PR titles. Real example: a tick fixed broken /now page links but the PR ended up titled "chore: discretionary website tick" because Claude didn't write a PR_BODY.md first item the harness could use. New tier-2 fallback: API-direct call to Haiku with the diff, asking for a one-line conventional-commit subject. Single-shot, no tool use, ~$0.005 per call, ~1-2s latency. Only fires when PR_BODY.md is missing or empty -- when Claude writes a good first item, that's still preferred (free, semantic, in his voice). New helper `claude_complete` does the API call generically: curl POST /v1/messages, returns text. Reusable for future in-harness thinking tasks (classification, summarization, etc.). Model defaults to Haiku via new optional IGOR_MODEL_THINKING env var; documented in .env.example. Three-tier subject derivation now: 1. PR_BODY.md first "What this PR does" item -- preferred 2. API-generated from diff -- when PR_BODY misses 3. Hardcoded fallback -- when API also fails Both tier-1 and tier-3 call sites updated to pass worktree path so the diff is accessible to the API tier.

joshtronic added 1 commit

2026-05-19 03:18:56 +00:00

feat: api-derived commit subjects when PR_BODY is empty

Lint / check-sync (push) Successful in 4s

Details

Lint / check-sync (pull_request) Successful in 3s

Details

41d83ff656

Generic fallback subjects ("chore: discretionary website tick")
were unhelpful in PR titles. Real example: a tick fixed broken
/now page links but the PR ended up titled "chore: discretionary
website tick" because Claude didn't write a PR_BODY.md first
item the harness could use.

New tier-2 fallback: API-direct call to Haiku with the diff,
asking for a one-line conventional-commit subject. Single-shot,
no tool use, ~$0.005 per call, ~1-2s latency. Only fires when
PR_BODY.md is missing or empty -- when Claude writes a good
first item, that's still preferred (free, semantic, in his
voice).

New helper `claude_complete` does the API call generically:
curl POST /v1/messages, returns text. Reusable for future
in-harness thinking tasks (classification, summarization, etc.).
Model defaults to Haiku via new optional IGOR_MODEL_THINKING
env var; documented in .env.example.

Three-tier subject derivation now:
  1. PR_BODY.md first "What this PR does" item -- preferred
  2. API-generated from diff -- when PR_BODY misses
  3. Hardcoded fallback -- when API also fails

Both tier-1 and tier-3 call sites updated to pass worktree path
so the diff is accessible to the API tier.

joshtronic merged commit 3a9ebbf8a9 into master

2026-05-19 03:19:31 +00:00

joshtronic deleted branch feat/api-derived-commit-subject

2026-05-19 03:19:31 +00:00

joshtronic referenced this pull request from a commit

2026-05-19 03:19:32 +00:00

Merge pull request 'feat: api-derived commit subjects when PR_BODY is empty' (#37) from feat/api-derived-commit-subject into master