| name | cncf-fortio-reviewer |
| description | Review Fortio using its official documentation and repository in the App Definition and Development / Continuous Integration & Delivery category. Fortio is an open source load testing library, command-line tool, and server application written in Go. Originated as Istio's performance characterization tool (in particular proxy overhead), Fortio has evolved into a versatile tool for load testing and performance benchmarking of HTTP, gRPC, and TCP services. Among other options it enables users to generate a specified query-per-second (QPS) load and records detailed latency histograms, facilitating the analysis of performance metrics. The server component offers a straightforward web UI and REST API, allowing users to initiate tests and visualize results through graphical representations. Beyond load testing, Fortio provides server-side features akin to httpbin, including request echoing with headers, configurable latency or error responses, TCP echoing and proxying, HTTP fan-out, and support for gRPC echo and health checks. These capabilities make Fortio a versatile tool for debugging and testing high-performance services in cloud-native environments. As an organization set of git repositories, is also a growing set of reusable libraries for writing Cloud Native Go code and CLIs. |
| version | 1.0.0 |
| since | 2026-08-29 |
| last_modified | 2026-08-29 |
| authors | ["platform-engineering"] |
| stability | stable |
| min_platform_version | {"codex":"unknown","amazon-q":"unknown","antigravity":"unknown","auggie":"unknown","bob":"unknown","claude-code":"unknown","cline":"unknown","codebuddy":"unknown","continue":"unknown","costrict":"unknown","crush":"unknown","github-copilot":"unknown","gitlab-duo":"unknown","factory":"unknown","forgecode":"unknown","opencode":"unknown","openhands":"unknown","cursor":"unknown","roo-code":"unknown","kiro":"unknown","junie":"unknown","gemini-cli":"unknown","iflow":"unknown","kilocode":"unknown","kimi":"unknown","lingma":"unknown","pi":"unknown","qoder":"unknown","qwen":"unknown","windsurf":"unknown","ollama":"unknown"} |
| deprecated_since | null |
| replaces | null |
| supersedes | [] |
| changelog | [{"version":"1.0.0","date":"2026-08-29","change":"Initial generated production-ready SDLC / DevSecOps skill"}] |
Cncf Fortio Reviewer
Purpose
Review and operate Fortio using current official documentation, repository evidence, and its CNCF Landscape classification without treating Landscape inclusion as endorsement.
Goal and behavioral contract
The authoritative Goal and artifact references are defined in descriptor.yaml. Capability boundaries, identity and delegation requirements, tool permissions, data boundaries, invariants, approval requirements, output contract, and operational limits are defined in contract.yaml. MCP/A2A trust boundaries and the reviewed execution closure live in integrations/ and dependencies.yaml; ASPS and assurance requirements live in assurance.yaml.
Treat those declarations as mandatory execution constraints. skcr validates requirements but does not claim verification or enforce them at runtime.
When to use
- Fortio code, configuration, APIs, deployment, integrations, dependencies, upgrades, or operations are in scope.
- A technology choice or migration involving Fortio requires evidence-backed assessment.
Operating model
- Detect the installed or proposed version and deployment model before giving version-sensitive guidance.
- Use current official documentation and repository evidence; use the CNCF Landscape only for classification metadata.
- Inspect boundaries with identity, secrets, network, storage, dependencies, observability, upgrades, rollback, and disaster recovery.
Spec-Driven Change Context
- Treat repository specs, ADRs, runbooks, change proposals, design notes, and task files as durable context that outlives a chat session.
- For non-trivial changes, prefer a checked-in change artifact or equivalent proposal/design/tasks record before implementation begins.
- Capture requirement deltas explicitly: added, modified, removed, deprecated, or unchanged behavior.
- Keep implementation tasks traceable to acceptance criteria, affected specs, validation commands, and owners.
- During verification, compare the implementation against the proposal, design decisions, task checklist, and spec deltas.
- After completion, sync or archive completed change artifacts so the repository's source of truth reflects the final behavior.
- If the repository has no spec workflow yet, report the missing artifact and provide a minimal proposal/spec/tasks outline instead of relying on chat-only intent.
Skill-Specific Review Scope
- CNCF classification: App Definition and Development / Continuous Integration & Delivery
