neuron-explorer
Qwen3.5‑4B 전용 조향형 뉴런 탐색기, 모든 MLP 뉴런을 밀어 결과를 보관·탐색
Coldworks가 풀 리퀘스트를 검토하고 팀 결정 내용을 기억해 반복 판단을 자체 체크로 전환합니다
Coldworks reviews your pull requests, remembers what your team decided, and turns the judgments it keeps repeating into checks you own.
개발 도구Python · TypeScriptGitHub @coldworkshq접속 불안정운영자 미확인
써 보셨어요? 한 번만 눌러 주세요. 로그인은 필요 없어요.
아직 감지된 업데이트가 없습니다. GitHub 릴리스가 나오면 여기에 보입니다.
개인 계정의 공개 저장소 소유자는 GitHub로 로그인해 운영자를 확인하고 소개를 직접 관리할 수 있습니다. 관리자 승인은 필요하지 않습니다.
로그인한 뒤 확인 파일을 만들어 이 저장소의 기본 브랜치에 30분 안에 커밋해 주세요. 다른 브랜치나 포크의 파일은 인정하지 않습니다. 파일을 올린 뒤 아래에서 확인하면 관리자 승인 없이 관리할 수 있습니다. 자격을 유지하려면 파일을 남겨 두세요.
로그인이 필요하면 로그인 화면으로 이동합니다. 로그인 후 이곳으로 돌아와 원하는 확인 버튼을 다시 눌러 주세요.
프로젝트 폴더에서 /nomorevibe verify를 실행하면 소유권을 확인하고 소개를 직접 관리할 수 있습니다.
1분 만에 확인하기Risk-routed code review. 62 open, 5 need you.
저장소 README에서 가져옴
README 전체를 불러오는 중입니다. 아래는 저장된 발췌입니다.
Most pull requests don't need a human.
Doug works out which ones do.
Every AI code reviewer on the market runs a language model over every diff. That makes their cost scale with the exact thing coding agents are inflating, and it still leaves a person reading bot comments on 100% of pull requests. Doug inverts the attention: most PRs clear, and only the small fraction that carries real risk gets a human. When the reader is on, that routing verdict still comes from an LLM reading the diff — the deterministic rules are the labeled fallback, not a claim that production is model-free.README 전문 보기 ↗[!IMPORTANT] This repository is retired, as of 2026-10-19. On retirement it is renamed
coldworkshq/doug-archiveand archived, so it is read-only. Work continues in the new private repositorycoldworkshq/coldworks. In this repository, every reference tocoldworkshq/coldworksorcoldworks#Nmeanscoldworkshq/coldworks-archive, the repository that held that name before the retirement.
Coldworks works out which ones do.
Every AI code reviewer on the market runs a language model over every diff. That makes their cost scale with the exact thing coding agents are inflating, and it still leaves a person reading bot comments on 100% of pull requests. Coldworks inverts the attention: most PRs clear, and only the small fraction that carries real risk gets a human. When the reader is on, that routing verdict still comes from an LLM reading the diff — the deterministic rules are the labeled fallback, not a claim that production is model-free.
This repository is the pull request reviewer in Coldworks, called Reviews on coldworks.dev. It keeps its codename, doug, in names you type: the repository, the Python package, the doug-backtest command, and the DOUG_* settings.
Route, never block. The PR proceeds either way. Coldworks only decides who has to look. Tools that block get disabled.
Never write code, never open a PR. The moment it authors, it owns the authorship.
Publish the miss rate. Every quarter, including the incidents that came from PRs it cleared. A gate that never publishes its errors is a marketing claim; one that does can survive being wrong. The scoreboard is live; the miss-rate number is not yet — miss_rate stays null until enough adjudications exist.
Live scoring (production sets DOUG_READER=1) is an LLM diff-read, unless a repository turns its deep read off on /dashboard/settings — that setting narrows, never widens. The deterministic fallback looks at cheap structural signals, including:
Diff size is deliberately de-weighted. It predicts poorly once the rest are controlled for. Rolling-window hotspot learning and several shape rules exist in the backtest CLI only, not in the live App path.
api/ — Python 3.14 + FastAPI, managed with uv. doug/reader.py (LLM scoring when enabled), doug/worker.py (drain + check run), doug/check_run.py, doug/features.py + doug/scoring.py (deterministic fallback). POST /webhooks/github verifies, records, and enqueues a review job, then 202s. GET /v1/queue is the token-gated ledger queue; GET /v1/showcase/queue and GET /v1/showcase/scoreboard are the public dogfood surfaces.web/ — Next.js 16 + Tailwind 4 + shadcn/ui. Landing, /queue, /docs, /scoreboard, WorkOS sign-in, and the signed-in /dashboard (ledger, repositories, and /dashboard/settings — flag line, PR comment, deep read, per repository). Public pages fetch /v1/showcase/* when the API is up, and fall back to a bundled fixture when it isn't.console/ — Operator console (Next.js). Shares the root npm workspaces lockfile with web/.make dev # API on :8000, web on :3000
make test # API + Node workspace tests
make lint # ruff + eslint
npm ci # install web + console from the root lockfile
Services ship Dockerfiles built for Cloud Run (respect PORT, scale to zero). The API still uses an app-dir build context; Node apps must be built from the monorepo root because of npm workspaces:
gcloud run deploy doug-api --source api
docker build -f web/Dockerfile -t doug-web .
docker build -f console/Dockerfile -t doug-console .
# Prod path: api/deploy/gcp.sh web|console builds via Cloud Build, then
# gcloud run deploy --image …
#
# Before the first Node image deploy, create the Artifact Registry repo
# (or re-run setup): PROJECT=doug-prod0 ./api/deploy/gcp.sh setup
#
# console is IAM-gated and not in CI — after a root lockfile / Dockerfile
# change, rebuild it with: PROJECT=doug-prod0 ./api/deploy/gcp.sh console
Early preview, dogfooding on this repository. The reviewer runs as a GitHub App, installed as dougs-review: webhook ingest, a durable worker, a neutral check run on every PR (ADR-0010). Merge to main deploys API + web (ADR-0009). It is not a self-serve product for other orgs yet.
The LLM reader is the scoring path when enabled (ADR-0004). The 2026-07 probe's AUC 0.69 / 0.67 is that probe, not a measurement of the shipped 100k-char reader (ADR-0012). Deterministic rule weights remain priors.
Not yet: outside installs, first published miss rate, Pattern Garden MCP server.
The self-serve measurement tool is still doug-backtest: replay a public repo's merged history, label defect-inducing changes via revert anchors, and plot capture against a size-only baseline.
FSL-1.1-ALv2 — Functional Source License. Read it, run it internally, modify it, learn from it. The one thing you can't do is ship it as a competing commercial product or service. It converts to Apache-2.0 automatically two years after each version is published.
Source-available rather than open source, and deliberately so: the point is freedom without free-riding, not enclosure.