{"name":"b612","description":"Japanese-market code review agent. Returns review checklists, industry requirement presets with mandatory Japanese legal checks, field-tested failure patterns from real client projects, and scans code you send to report risky spots as file:line with why and how to fix. Deterministic checks — no LLM inference, so calls are fast and cheap. Covers regulations that global tools do not: 景表法 / 特商法 / 薬機法 / インボイス / 電帳法 / 宅建業法 / 介護保険法.\n\n【日本語】日本の実務（法令・商習慣）と実案件の失敗から作ったレビュー方法論のエージェント。レビュー観点・業種別の必須要件・実戦パターンを返し、送られたコードは実際に検査して行番号で指摘する。","version":"0.1.0","url":"https://b612-a2a.vercel.app/a2a/v1","preferredTransport":"JSONRPC","protocolVersion":"0.3","capabilities":{"streaming":false,"pushNotifications":false},"defaultInputModes":["text/plain","application/json"],"defaultOutputModes":["text/plain"],"skills":[{"id":"principles","name":"Review principles / b612 の思考原則","description":"Returns b612's review principles: no speculation without evidence, the three questions to ask before implementing, and the rules against swallowing errors. Read this before reviewing or implementing.\n\n【日本語】レビューや実装を始める前に読む思考の核（NO SPECULATION・実装前の3問自問・5原則・握りつぶし禁止）を返す。","tags":["code-review","principles","engineering-discipline","japanese"],"examples":["What principles should I follow before reviewing this code?","b612 の思考原則を教えて"],"inputModes":["text/plain","application/json"],"outputModes":["text/plain"]},{"id":"review-checklist","name":"Review checklist by target type / 対象別レビュー観点","description":"Returns a concrete review checklist for a given target type (landing page, corporate site, e-commerce, API, SaaS, game, form). Written for the Japanese market, including legal and UX points that generic checklists miss.\n\n【日本語】レビュー対象の種類に応じた観点リストを返す。対応: lp, hp, ec, api, saas, game, form, generic","tags":["code-review","checklist","landing-page","ecommerce","saas","japanese"],"examples":["Give me a review checklist for a landing page","EC サイトを見るときの観点は？"],"inputModes":["text/plain","application/json"],"outputModes":["text/plain"]},{"id":"patterns","name":"Field-tested failure patterns / 実戦パターン","description":"Returns hard-won lessons from real Japanese client projects: the failure modes that actually happened, why they were invisible, and the decisions that worked. Searchable by keyword (LINE, payments, booking, printing, responsive).\n\n【日本語】実案件で踏んだ失敗と、効いた意思決定の蓄積（公開版・案件固有名なし）。既定は見出し索引、query で該当節を返す。","tags":["postmortem","lessons-learned","debugging","japanese","line-messaging-api"],"examples":["What goes wrong with LINE Messaging API integrations?","決済まわりで踏みやすい罠は？"],"inputModes":["text/plain","application/json"],"outputModes":["text/plain"]},{"id":"domain-preset","name":"Industry presets (Japan) / 業種別プリセット","description":"Returns required data models, edge cases, mandatory Japanese legal checks and anti-patterns for a given industry: e-commerce, booking, healthcare, real estate, HR, accounting, nursing care, restaurants, LINE bots and 25 more. Covers Japanese regulations (Act against Unjustifiable Premiums, Specified Commercial Transactions Act, Pharmaceuticals and Medical Devices Act, qualified invoice system, Building Lots and Buildings Transaction Business Act).\n\n【日本語】業種ごとの必須モデル・エッジケース・必須法令・アンチパターンを返す。対応: accounting, ai-chat, android, beauty, blog, booking, chat, community, corporate, corporate-story, crm, ec, event, fukushi, game, healthcare, hr, instagram, inventory, ios, line, lms, lp, pos, project, rag, realestate, restaurant, retrogame, saas, subscription, survey, task","tags":["japanese-law","compliance-jp","keihyoho","tokushoho","yakkiho","invoice-jp","domain-model","requirements"],"examples":["What are the legal requirements for a Japanese e-commerce site?","What must a booking system in Japan handle?","予約システムの必須要件を出して"],"inputModes":["text/plain","application/json"],"outputModes":["text/plain"]},{"id":"scan-code","name":"Scan code and report findings / コード検査","description":"Actually reads the source you send and reports risky spots as file:line, with why it is dangerous and how to fix it. Deterministic checks (no LLM inference, no per-call AI cost). Rules come from real production incidents: swallowed errors, silent zero-row updates, hardcoded secrets, duplicated timers, destructive SQL, XSS, platform payload limits. Distinguishes 'zero findings' from 'nothing could be scanned'.\n\n【日本語】送られたコード本文を実際に検査し、危ない箇所を「ファイル:行」で指摘する。AI 推論を使わない決定的検査。","tags":["static-analysis","code-review","security","bug-detection","japanese"],"examples":["Scan this file for swallowed errors and hardcoded secrets","このコードを b612 で検査して"],"inputModes":["text/plain","application/json"],"outputModes":["text/plain"]},{"id":"rules","name":"Detection rules / 検出ルール一覧","description":"Returns the full list of detection rules used by scan-code: id, severity, why it is dangerous, and how to fix it. Published so callers can see exactly what is checked.\n\n【日本語】コード検査で適用しているルール（ID・重大度・なぜ危険か・直し方）の一覧を返す。","tags":["static-analysis","transparency","rules"],"examples":["What rules does your scanner apply?","検出ルールの一覧をください"],"inputModes":["text/plain","application/json"],"outputModes":["text/plain"]}],"provider":{"url":"https://hakuto-0209.com","organization":"HaneruTo"},"documentationUrl":"https://b612-a2a.vercel.app/terms","supportsAuthenticatedExtendedCard":false,"securitySchemes":{"b612ApiKey":{"type":"apiKey","name":"x-b612-key","in":"header","description":"b612 license key. Contact the provider to obtain one. / b612 のライセンスキー。ヘッダーで送る。"}},"security":[{"b612ApiKey":[]}],"supportedInterfaces":[{"url":"https://b612-a2a.vercel.app/a2a/v1","protocolBinding":"JSONRPC","tenant":"","protocolVersion":"1.0"},{"url":"https://b612-a2a.vercel.app/a2a/v1","protocolBinding":"JSONRPC","tenant":"","protocolVersion":"0.3"}]}