conventions-check

Check a diff against Polar's written conventions in server/AGENTS.md and clients/AGENTS.md — module structure, repository and service patterns, session types, auth dependencies, test organisation, Orbit Box usage, i18n placement. Use before opening a PR or when the user asks whether a change follows Polar's conventions.

跳到安装

仓库: polarsource/polar
最近来源活动: 2026年8月19日 16:35
检测到的 SKILL.md 语言: 英语
星标: 10,263
分支: 784

安装方式

默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

直接命令不会经过审查 Prompt；运行前请先检查来源。

npx skills add https://github.com/polarsource/polar --skill conventions-check

命令会保持在同一行。复制前请横向滚动并检查完整内容。

想先保存到本地？可下载 SkillsMP 当前能够提供的文件。

检查来源文件

决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。

SKILL.md

来源说明 · 只读预览

name: conventions-check
description: Check a diff against Polar's written conventions in server/AGENTS.md and clients/AGENTS.md — module structure, repository and service patterns, session types, auth dependencies, test organisation, Orbit Box usage, i18n placement. Use before opening a PR or when the user asks whether a change follows Polar's conventions.
license: MIT
metadata: {"author":"polar","version":"1.0.0"}

# Conventions Check (Polar) The handle is the **diff**. The evidence is a list of **places it breaks a rule written in `AGENTS.md`**. ## Rule `server/AGENTS.md` and `clients/AGENTS.md` are the source of truth. Read them in full before reviewing. Do not work from memory, and do not invent a rule that is not in those files. If you want to flag something they do not cover, put it under Question. ## Owned elsewhere Do not report these; another lens covers them, and duplicate findings are what makes a review tiring to read. | Topic | Owner | |---|---| | Anything an Accepted ADR covers | `adr-check` | | Reinventing an existing helper | `reuse-check` | | Agent-generated noise, redundant tests | `slop-check` | | API contract, schemas, SDK impact | `api-surface-review` | | Migrations, tasks, deploy ordering | `ship-safety` | | Billing domain behaviour | `billing-review` | What is left for you: module structure, the repository and service patterns, read versus write sessions, auth dependencies and per-module `auth.py`, test layout and fixtures, Orbit `<Box />` usage, the 250-line frontend file limit, i18n placement. ## Output ``` ## Conventions ### 🔴 Blocking - `file:line` — <claim>. Fix: <fix> ### 🟠 Should fix - `file:line` — <claim>. Fix: <fix> ### 🟡 Question - `file:line` — <question> ### Verdict ✅ Clean | ❌ n blocking, n should-fix ``` Quote the rule from `AGENTS.md` in the claim. High-confidence findings only. Never flag unchanged code.

在 GitHub 查看

返回搜索返回安装

local-environment

Local development environment management for Polar using Docker

2026-09-10

api-surface-review

Review changes to Polar's API contract — Pydantic schemas, FastAPI endpoints, OpenAPI output and the generated SDKs. Checks public vs private exposure, schema shape and naming, and whether the change breaks merchants or the generated clients. Use when a diff touches schemas.py, endpoints.py, docs/openapi.json or sdk/, or when the user asks whether an API change is breaking.

2026-08-19

billing-review

Review a diff that touches Polar's billing domain — subscriptions, cycles and crons, orders, billing entries, meters and usage, discounts, checkout, payments and dunning, refunds, disputes, payouts, wallets, tax and invoices. Use before opening a PR that changes money movement or subscription lifecycle, when the user asks for a billing review, or when a reviewer needs the domain rules the team enforces in review but that no linter catches.

2026-08-19

查看这个仓库的全部 Skills

conventions-check

来源信息

安装方式

检查来源文件

同仓库更多 Skills

同仓库更多 Skills