8 件（Chronote-gg のリポジトリ） ・ 人気順
概要と使いどころ
Configure and debug MCP servers for Claude Code, OpenCode, and Codex CLI, including auth headers, scope, and validation checks. Use when MCP tools fail to connect, when an MCP server returns 401/404/HTML, or when adding a new MCP server to this repo.
日本語の概要は準備中です。原文の説明を表示しています。
Use to process automated PR review feedback (Copilot, Greptile, Codex) and iterate until all AI threads are addressed, checks are green, and the PR is merge-ready. Trigger when the user says "address review feedback", "recycle reviews", or references an automated reviewer.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze Chronote product adoption with PostHog and Langfuse, including active users, meetings, feature usage, AI telemetry, and privacy-safe resolution of active Discord guild IDs to live server names.
日本語の概要は準備中です。原文の説明を表示しています。
Query aggregate Langfuse cost, volume, latency, and model telemetry efficiently with Metrics API v2. Use for dashboards, rollout checks, usage summaries, and cost or latency comparisons; use Observations API v2 instead when individual rows are actually required.
日本語の概要は準備中です。原文の説明を表示しています。
Configure and debug MCP servers for OpenCode, Codex CLI, and Claude Code, including auth headers, scope, and validation checks. Use when MCP tools fail to connect or when adding a new MCP server.
日本語の概要は準備中です。原文の説明を表示しています。
Use every time you push a commit to an active pull request, to verify the PR is truly stable before reporting merge readiness. Covers the post-push wait window, AI review audit (Copilot/Greptile/Codex), and the gh commands to snapshot PR state. Trigger on "I pushed" or "is the PR ready to merge".
日本語の概要は準備中です。原文の説明を表示しています。
Use when a change affects user-visible behavior at docs.chronote.gg and needs public documentation. Covers where docs live (apps/docs-site vs docs/), authoring checklist, yarn docs:check, and Algolia config. Trigger when the user mentions docs, release notes, what's-new, or user-facing PR changes.
日本語の概要は準備中です。原文の説明を表示しています。
Investigate errors, incidents, or product ideas using both internet research and repo-wide codebase research, then propose a concrete changeset plan with clarifying questions before any implementation. Use when a user asks to investigate, root-cause, or plan changes, or when an Issue or PR is referenced and needs a plan.
日本語の概要は準備中です。原文の説明を表示しています。