K6 Docs

作者 grafana1ccacf29049fApache-2.0279 個星標收錄於 2026年10月8日更新於 2026年10月8日儲存庫今天更新

Write or review k6 documentation across the three k6 repositories - k6-DefinitelyTyped (TypeScript types), k6-docs (user documentation), and k6 (release notes / changelog). Applies k6 doc style conventions, generates TypeScript type definitions, drafts release notes, and validates examples by running them against k6@master. Use when working on k6 documentation, the k6 changelog, the k6 release notes, k6 API reference, k6 TypeScript types, load testing docs, or when the user asks to write, edit, or review anything in the k6, k6-docs, or k6-DefinitelyTyped repos - even if they don't explicitly say "documentation".

AI 產生的概覽

在三個 k6 儲存庫中撰寫與審閱 k6 文件、TypeScript 型別定義與發行說明。

功能
此技能引導代理在 k6-DefinitelyTyped、k6-docs 與 k6 儲存庫中撰寫或審閱 k6 文件。它會套用 k6 文件風格慣例,草擬發行說明與變更記錄,產生 TypeScript 型別定義,並透過在 k6@master 上執行來驗證程式碼範例。它附帶參考資料、檢查清單、範本,以及用於取得提取要求、尋找分支、格式化與測試 TypeScript、驗證連結和更新團隊成員的 shell 指令碼。
適用情境
適用於處理 k6 文件、k6 變更記錄或發行說明、k6 API 參考或 k6 TypeScript 型別時。也適用於撰寫、編輯或審閱 k6、k6-docs 或 k6-DefinitelyTyped 儲存庫中任何內容的要求,即使未明確提到文件。
執行需求
需要本機檢出 k6 儲存庫的 master 分支、用於透過 go run 執行範例的 Go 工具鏈,以及執行附帶指令碼的 shell 環境。部分指令碼可能需要網路存取與憑證,以進行取得提取要求等儲存庫操作。

k6 Documentation

Document or review k6 features across three repositories: k6-DefinitelyTyped (TypeScript types), k6-docs (user documentation), and k6 (release notes).

Workflow

Pick the workflow that matches the user's intent:

  • Write documentation: follow references/workflows/write.md [blocked]
  • Review documentation: follow references/workflows/review.md [blocked]

Quick References

  • Repository structure & feature type identification [blocked]
  • TypeScript patterns & troubleshooting [blocked]
  • Testing workflow with parallel subagents [blocked]
  • agent-browser command reference [blocked]
  • Troubleshooting guide [blocked]

Critical Rules

  • Never push automatically - always ask first
  • Never chain commands with && or ; - run each command separately (prevents failures)
  • Only document user-facing features - not internal implementation
  • Use 1. for every numbered list item (not 1., 2., 3.)
  • Test every code example against k6@master before committing
  • No Co-Authored-By: Claude or AI attribution in commits

Validating examples (always run before committing)

Every code example in k6 documentation and release notes must execute cleanly against k6@master. The minimum loop:

bash
# 1. cd into the k6 repo (not k6-docs or k6-DefinitelyTyped)cd ~/path/to/k6
# 2. Make sure you're on master at the latest commit (the contract is k6@master)git checkout mastergit pull
# 3. Run each example as a separate command (no &&)go run . run /path/to/script.js

If the run fails: read the error, fix the example in the source (doc or release note), re-run. Do not commit a change whose example doesn't run clean against current master. For the full multi-example workflow with parallel subagents, see references/testing-workflow.md [blocked].

來源與署名

來源:grafana/skills位於skills/grafana-k6/k6-docs提交1ccacf2

授權條款: Apache-2.0

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

檢舉或申請下架

更多來自 grafana/skills 的技能

React 19 Plugin Migration

grafana

指導將 Grafana 外掛遷移至 React 19 相容,依序完成建置、相依性與原始碼修改步驟。

Software Development279今天更新

Plugin Bundle Size

grafana

指導使用 React.lazy、Suspense 與 webpack 程式碼分割來最佳化 Grafana 應用程式外掛的打包體積。

Software Development279今天更新

Grafana Scenes

grafana

使用 @grafana/scenes 框架建置 Grafana 外掛頁面,涵蓋場景、面板、變數與下鑽導覽。

Software Development279今天更新

Check Npm

grafana

對 JS/TS 儲存庫的 npm、yarn 或 pnpm 設定進行唯讀供應鏈強化稽核。

Security279今天更新

Mimir

grafana

指導架設與維運 Grafana Mimir,用於可擴充、多租戶、長期的 Prometheus 與 OTLP 指標儲存。

DevOps & Cloud279今天更新

K6 Trend Analysis

grafana

Analyze Grafana Cloud k6 test run trends over time. Detects slow metric drift (e.g., P95 latency creeping up while still passing thresholds), computes headroom to thresholds, flags anomalies, and recommends threshold tightening. Use when the user asks about test performance trends, wants to know if metrics are degrading, asks whether thresholds should be tightened, or wants a health check across recent runs for a specific test. Trigger on phrases like "how is my test trending", "is P95 getting worse", "check for performance regression", "should I tighten thresholds", "are my tests degrading", "show me trends for test X", "analyze my k6 test runs", or "is my test getting slower". Also trigger when a user asks to check all tests in a project -- run this skill once per test and synthesize.

待分類279今天更新