Skip to content

kaizen: 単一の builder-agent テストを主要モジュール別の TypeScript テストへ分割しました。 (#75)#87

Merged
s-hiraoku merged 3 commits into
mainfrom
kaizen/issue-75-split-test-coverage-per-module-after-the-js-to-t
Jul 5, 2026
Merged

kaizen: 単一の builder-agent テストを主要モジュール別の TypeScript テストへ分割しました。 (#75)#87
s-hiraoku merged 3 commits into
mainfrom
kaizen/issue-75-split-test-coverage-per-module-after-the-js-to-t

Conversation

@s-hiraoku

Copy link
Copy Markdown
Contributor

Closes #75

Summary

単一の builder-agent テストを主要モジュール別の TypeScript テストへ分割しました。
AgentRunner のフォールバック分類、CLI 終了コード、artifacts、SelfReview、types の回帰テストを整理・追加しました。
既存の検証観点は移植し、旧 test/builder-agent.test.js は削除しました。

Builder notes

検証: set -e; npm test; npm run validate:json; test -f skills/gh-link-issue-pr/SKILL.md && test -f skills/kaizen-bug-router/SKILL.md && test -f skills/pr-guardian/SKILL.md が成功。protected path の変更なし。

Provider evidence:

  • codex: exitCode=0, status=selected, failureClass=none, fallbackReason=none, payloadSource=last-message
    Selected backend: codex
    Final payload source: last-message

Verification

  • npm test
  • npm run validate:json
  • test -f skills/gh-link-issue-pr/SKILL.md && test -f skills/kaizen-bug-router/SKILL.md && test -f skills/pr-guardian/SKILL.md

Verifier

verifier: open_pr_with_warning
summary: Open PR with warning and 2 should_fix item(s); risk is medium.
notes: evidence_grade=reported
risk=medium
confidence=60
should_fix=Verification output contains a non-blocking risk signal.; Verification output contains a non-blocking risk signal.

Kaizen risk policy

Verifier cleared PR with warning: Open PR with warning and 2 should_fix item(s); risk is medium.

Changed files: 12
Changed lines: 2893

@coderabbitai

coderabbitai Bot commented Jul 5, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@s-hiraoku, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 59 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Repository: kaizen-agents-org/coderabbit/.coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 7d165446-b93b-4a61-bf15-d79a50c16b60

📥 Commits

Reviewing files that changed from the base of the PR and between 185c9c6 and 544c656.

📒 Files selected for processing (15)
  • .gitignore
  • package.json
  • scripts/run-tests.js
  • test/agents/AgentRunner.test.ts
  • test/artifacts.test.ts
  • test/builder-agent.test.js
  • test/builder/BuilderAgent.test.ts
  • test/cli.test.ts
  • test/helpers.ts
  • test/review/SelfReview.test.ts
  • test/types/BuildRequest.test.ts
  • test/types/BuildResult.test.ts
  • test/types/DiscoveredIssue.test.ts
  • test/types/KaizenLoopPayload.test.ts
  • test/types/contracts.test.ts
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch kaizen/issue-75-split-test-coverage-per-module-after-the-js-to-t

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@s-hiraoku

Copy link
Copy Markdown
Contributor Author

PR Guardian pass 1/5 summary:

  • Final mergeability: mergeable, non-draft, mergeStateStatus CLEAN.
  • Required checks: passing. Branch protection requires test; test passed on CI run 28726334977. CodeRabbit status is also passing.
  • Watched runs: gh run watch 28726334977 --exit-status completed successfully; the run had already finished with success.
  • Fixes pushed: none needed.
  • Feedback inspected: paginated GraphQL read of PR comments, reviews, and reviewThreads completed with hasNextPage=false for each connection. No review threads or reviews were present.
  • Feedback addressed/skipped: CodeRabbit posted a rate-limit/review-availability notice only; it did not contain actionable code feedback, so no code change was required.
  • Remaining blockers: none found. I did not merge the PR.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 827747b561

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread test/agents/AgentRunner.test.ts
@s-hiraoku s-hiraoku merged commit cca23cb into main Jul 5, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Split test coverage per module after the JS-to-TS migration

1 participant