Jak używać
- Skopiuj polecenie instalacji i sprawdź źródła przed instalacją we własnym środowisku agenta.
- W oryginale sprawdź wymagane narzędzia, dane dostępowe i obsługiwane środowiska.
- Opisz dane wejściowe i oczekiwany rezultat; porównaj wynik ze źródłami.
npx skills add https://github.com/puppo/fastify-contribute-skills --skill fastify-corePrzed rozpoczęciem
- Instalacja nie obejmuje subskrypcji modelu, limitu API ani uprawnień do plików.
- Gwiazdki i instalacje pokazują aktywność, a nie niezależny test jakości lub bezpieczeństwa.
Treść z repozytorium z zachowaniem nagłówków, przykładów, kodu, tabel, linków i obrazów.
Fastify Core Maintainer Skill (fastify/fastify)
Use this skill when reviewing a pull request, implementing a feature, or fixing a bug inside the [`fastify/fastify`](https://github.com/fastify/fastify) core framework repository.
Companion Skills Boundary: - When reviewing a pull request or diff, pair this skill with `fastify-code-review` for the standardized review flow, severity classification, and Fastify maintainer tone. - For@fastify/*plugin and utility repositories, use `fastify-plugins`. - For the centralized reusable workflows repository (fastify/workflows), use `fastify-workflows`. - For the official Fastify website repository (fastify/website,fastify.dev), use `fastify-website`.
Repository maps, tool versions, and workflow defaults below are orientation examples. Confirm them in the target checkout before applying them; its configuration and contribution rules determine applicability. Source root observed on 2026-10-14: fastify/fastify at `e222f53`.
Keep core minimal: anything that can be implemented as a plugin should be a plugin. For new core behavior, assess existing hooks, decorators, and other extension points first; require a concrete reason for core placement. Ask when plugin feasibility or the rationale is unclear.
Step 1: Verify Target Branch, Governance & Local Scripts
- Branch & Version Line Check:
- Inspect
git branch --show-currentandpackage.json#version(main/nextvs maintenance branches5.x,4.x, etc.). - Read the target branch's contribution and release rules. Ordinary feature/bug-fix PRs should not bump versions where releases are reserved for maintainers; documented maintainer release changes follow their release process.
- Human-Opened PR Policy (`CONTRIBUTING.md`): Pull requests in
fastify/fastifymust be opened by a human. Prepare verified local patches, conventional PR titles (pull-request-title.yml), and review summaries for the human maintainer.
- Core Command Reference (`package.json#scripts`):
- Confirm these scripts and their bodies in the target checkout before running them. During review, follow
fastify-code-reviewrevision matching and isolation rules; generators must run only in a temporary checkout. - Unit tests:
npm run unit(borp) - Single unit test file:
npx borp -p test/<file>.test.js - 100% coverage gate (CI):
npm run coverage:ci-check-coverage(borp --coverage --check-coverage --lines 100) - Type tests:
npm run test:types(tstycheontest/types/*.tst.ts) - Single type test file:
npx tstyche test/types/<file>.tst.ts - JS/TS Linter:
npm run lint(eslintwithneostandard,max-len: 120,comma-dangle: never) - Markdown Linter:
npm run lint:markdown(markdownlint-cli2) - Regenerate Validators & Serializers:
npm run build:validation - Verify Generated File Integrity:
npm run test:validator:integrity
fastify/fastify Repository Layout
.
├── .borp.yaml # Test glob: test/**/*.test.js and test/**/*.test.mjs
├── .markdownlint-cli2.yaml # Markdown linter configuration
├── .npmrc # ignore-scripts=true, min-release-age=7, package-lock=false
├── CONTRIBUTING.md # Core governance, human-opened PR rule, LTS branches
├── eslint.config.js # neostandard + max-len 120 + .d.ts & test/types rules
├── fastify.js # Main entry point, server factory, routing & exports
├── fastify.d.ts # Root TypeScript declarations & server overloads
├── build/
│ ├── build-error-serializer.js # Generates lib/error-serializer.js via fast-json-stringify
│ ├── build-validation.js # Generates lib/config-validator.js via @fastify/ajv-compiler
│ └── sync-version.js # Syncs package.json version into fastify.js VERSION
├── lib/ # Core runtime modules (context, hooks, reply, request, route, etc.)
├── types/ # Modular .d.ts files imported by fastify.d.ts
├── test/
│ ├── *.test.js # Core unit tests (borp / node:test)
│ ├── same-shape.test.js # V8 hidden-class / monomorphic shape assertions
│ ├── bundler/ # webpack and esbuild bundle smoke tests
│ ├── diagnostics-channel/ # node:diagnostics_channel tests
│ ├── http2/ & https/ # HTTP/2 and TLS server tests
│ ├── internals/ # Direct unit tests of lib/* internals
│ ├── logger/ & stream/ # LoggerController/Pino and payload stream tests
│ └── types/ # TSTyche type tests (*.tst.ts) + test/types/tsconfig.json
├── integration/ # Production install + live server smoke test (server.js, test.sh)
├── scripts/
│ └── validate-ecosystem-links.js # Validates GitHub links in docs/Guides/Ecosystem.md
├── docs/
│ ├── Guides/ # User guides (Style-Guide.md, Ecosystem.md, Contributing.md)
│ └── Reference/ # API reference (Errors.md, Warnings.md, Hooks.md, Server.md, etc.)
└── .github/workflows/ # Core CI, coverage, CITGM, docs, and automation workflowsStep 2: Load Core Reference Guides
Load the reference file(s) matching the area of fastify/fastify affected by your task:
| Core Area | What It Covers | Reference |
|---|---|---|
| 1. Code & Architecture (`code`) | fastify.js and lib/*.js module map, build/ code generators (lib/config-validator.js & lib/error-serializer.js) and test:validator:integrity, lib/symbols.js, avvio plugin encapsulation (lib/plugin-override.js), lib/errors.js (FST_ERR_*), and lib/warnings.js (FSTWRN*, FSTSEC*, FSTDEP*). | references/code.md |
| 2. Best Practices, Performance & Types (`best-practices`) | V8 monomorphic shapes on Request/Reply (test/same-shape.test.js), request lifecycle hot-path discipline, ESLint (max-len: 120, comma-dangle: never), fastify.d.ts + types/*.d.ts 5-parameter generic propagation, and docs/ synchronizing rules (Errors.md, Warnings.md, Style-Guide.md, Ecosystem.md). | references/best-practices.md |
| 3. Testing & Type Testing (`test`) | borp unit testing (npm run unit) and 100% coverage (npm run coverage:ci-check-coverage), @matteo.collina/tspl (await p.completed), fastify.inject() vs fastify.listen({ port: 0 }), test/internals/, test/bundler/ (webpack & esbuild), integration/, and test/types/*.tst.ts (tstyche). | references/test.md |
| 4. Workflows & CI Gates (`workflows`) | Workflow domains in fastify/fastify/.github/workflows/: ci.yml (coverage-nix, coverage-win, test-unit, test-types, test-pino-compat, package), citgm.yml (citgm-core-plugins label), test-compare.yml, missing_types.yml, md-lint.yml, links-check.yml, lint-ecosystem-order.yml, pull-request-title.yml, and backport.yml. | references/workflows.md |
Core Non-Negotiable Checklist Before Completing Any Task
- Generated Files Integrity: For generator changes, confirm
build:validationandtest:validator:integrityin the checkout and regenerate during implementation. During review, verify committed output only in an isolated checkout. Never edit generated validators by hand; core'sbuild/source scripts and generated files inlib/are intentionally tracked. - Public Contracts: When public options, hooks, request/reply APIs, or error codes change, update the affected declarations, type tests, and reference docs. Test internal behavioral fixes without requiring unrelated public API edits.
- Tests, Coverage & Lint: Run relevant runtime/type tests and linters using the checkout's scripts. Run the configured coverage gate separately for runtime changes; focused test success alone does not establish coverage. Report unavailable checks as
Not runwith the reason.