- Skills
- 27
- 仓库
- 1
- 职业覆盖
- 1
- 场景覆盖
- 4
- Stars
- ★ 2.1w
Pydantic 的 Skills 27
poweruser-feature-audit
Independent power-user audit of a big new-feature PR. Research the feature domain from external sources before reading any implementation code, design the ideal test suite from a power-user's perspective, then gap-compare it against the PR to produce evidence-backed, precedent-linked review items. Use when a large feature PR (new provider API surface, new modality, new subsystem) needs an unbiased second opinion grounded in what the underlying APIs and real integrators require. Not a diff review.
initialize-worktree
Study a problem or GitHub issue in a fresh worktree, plan a fix, optionally implement it, and open the initial PR. Use when starting work on a new problem — not for advancing existing PRs.
i-have-adhd
Shape every response for an ADHD reader who reviews the work but does not do the coding — the agent does. Use whenever responding to ANY message — coding, debugging, planning, casual. Lead with the result or the decision. Surface anything needing the user's input as a structured question, never buried in prose they'll skim past. No preamble, no recap, no closers. State errors matter-of-factly. Make finished work visible. Trigger even on casual messages and even when brevity wasn't requested.
file-followup-issue
Capture a real, net-positive bug or improvement you discovered that is OUT OF SCOPE for the current PR — the PR already closes its issue and is stable, and the new work is non-trivial (adds its own decisions, carries uncertainty, or widens blast radius beyond what the issue needed). Opens a GitHub issue with full context for a future session and does NOT touch the current PR. NOT for trivial in-scope fixes (just do those) or non-issues (dismiss those).
docs-parity-reviewer
Use as the final documentation gate before a `pydantic-ai-harness` capability PR merges. Verifies that a user-facing change keeps the capability README under `src/pydantic_ai_harness/pydantic_ai_harness/` and its `docs/harness/` page in sync with each other and with the code, that every snippet is runnable, and that links follow repo convention. Reports gaps; does not edit. Skip it for changes that touch no harness capability or its docs.
complete-partial-pr
Evaluate and complete an issue or PR where the submitted patch fixes only a narrow symptom of the reported pain point. Use when a contribution may miss adjacent integration surfaces, provider/spec semantics, roundtrip behavior, tests, docs, or historical maintainer decisions.
branch-context
Branch-local durable PR state — issue brief, decisions log, and session handoffs. Read the brief, decisions and handoffs index every session; persist decisions as you work; hand off only on user request or explicit session turnover.
adopt-pr
Bootstrap branch-context on an existing PR that wasn't started via /initialize-worktree. Writes issue-brief.md from the linked issue(s) + current PR state, and backfills pr-decisions.md with decision-bearing entries from already-resolved review threads. Use when picking up a PR mid-flight (either yours or someone else's) without prior local context.
adding-a-provider-api-feature
Add a new provider API capability (prompt caching, strict/structured tool calling, thinking/reasoning effort, service tier, safety settings, logprobs, etc.) to Pydantic AI. Use when wiring a provider feature through the library — it enforces reasoning from the existing cross-provider abstraction before designing anything, and picking default-on vs opt-in deliberately. Not for adding a new model id (that's a different flow) or a bug fix.