Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

pstack: in Claude Code, every review seat runs on Claude; allow an external-CLI seat such as codex

オープン
  • 何か問題がありますか？
#809 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
45/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
typescript
領域
developer-experience, tooling

調査の方向性

Start with docs/harness/claude-code.md and its Models table, then trace how setup-pstack reads or writes pstack-models.mdc. Check the related tool mapping work in #601 for existing conventions. Done means Claude Code can run a configured external CLI reviewer and setup-pstack can detect Codex and offer it as a second family; the issue leaves the accepted role syntax open.

索引モデルが issue の本文から書いたものです。

説明

What happens

pstack's review panels are built on two model families. interrogate defaults Reviewer B to grok-4.7-xhigh-fast, arena tells the cross-judge to prefer a different family from the parent, and reflect puts the tooling reviewer on Grok.

In Claude Code the harness adapter (docs/harness/claude-code.md, Models table) maps any non-Claude slug to "omit model so the agent runs on the session model, and say so". The Agent tool only accepts opus, sonnet, haiku, fable. So every panel seat runs on Claude and the adversarial design collapses to one family, silently from the user's point of view unless they read the reply closely.

Why it matters

On 2026-10-24 we ran a read-only codex exec pass over a test suite that two Claude passes (the author and an Opus reviewer via interrogate-style prompts) had already reviewed. Codex found three defects in the project's own lint tests that both Claude passes had walked past; 27 of its 33 findings held. That is the signal the two-family design is meant to produce, and Claude Code users cannot get it through pstack today.

Proposal

Let a role line in pstack-models.mdc name an external CLI seat, and have the Claude Code adapter run that seat over Bash instead of dropping it to the session model. Concretely:

  • A value such as codex (or codex-review, or a generic cli:<command>) on interrogate reviewers, arena cross-judge pool and reflect tooling.
  • The adapter row: "a codex seat runs codex exec --sandbox read-only --ephemeral -o <report> - with the same reviewer prompt on stdin, from the checkout root, and the lead reads the report file as that reviewer's findings".
  • setup-pstack detects codex on PATH and offers it as the second family when the harness is Claude Code.

We have this working as a project skill (.claude/skills/codex-review with a bin/review brief|diff wrapper and a SessionStart hook that re-applies the two role lines after /setup-pstack regenerates the file). Happy to contribute the adapter row and the setup-pstack detection as a PR if the shape above is acceptable.

Related: #601 (tool mappings for Claude Code and Codex), #734 (running pstack inside Codex, which is the other direction).

主要言語
TypeScript
スター
13.9k
フォーク
1.4k
平均マージ
5時間 39分
マージ済み PR（30日）
145

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

cursor/plugins のほかの issue

cursor/plugins の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。