# HTTP API Openapi

> Keep HTTP handlers and OpenAPI (openapi.yaml) in sync. Use when adding/changing endpoints, request/response schemas, auth requirements, or error shapes.

- Skill: `aibot88/http-api-openapi` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add aibot88/http-api-openapi`
- Raw SKILL.md: https://api.skillmd.com/api/skills/aibot88/http-api-openapi/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Integrations & APIs
- License: MIT
- Author: aibot88 (https://skillmd.com/u/aibot88)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/aibot88/http-api-openapi

---


## Tooling assumptions

- Use a terminal runner with bash and git available.
- Prefer `make` targets when available; fall back to direct CLI commands when needed.

## Source of truth

- OpenAPI spec: `openapi.yaml` at the repo root.

## Typical workflow

1. Update `openapi.yaml` (paths, schemas, auth).
2. Validate the spec:

```bash
make validate-openapi
```

If `swagger-cli` isn’t installed:

```bash
npm install -g @apidevtools/swagger-cli
```

3. Implement the handler changes in Go (and keep auth consistent with the spec).
4. Run tests:

```bash
make test
```

## Project-specific notes

- Authenticated endpoints use Bearer token auth (see README’s Auth section).
- Be explicit about error responses and status codes in the spec when behavior changes.