Regenerate openapi.json and the frontend types after a change to a route or schema of the Django API (django-ninja). Use as soon as a schema or a route changes.
Installs into .claude/skills of the current project.
Are you the author of Regen Api?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/antoine-tena-regen-api)
---
name: regen-api
description: Regenerate openapi.json and the frontend types after a change to a route or schema of the Django API (django-ninja). Use as soon as a schema or a route changes.
---
Repo settings: !`env | grep -E '^(KILN_(BACKEND_DIR|FRONTEND_DIR|TEST_ENV)|PROJET_(BACK|FRONT|ENV_TEST))=' | sort`
(`PROJET_BACK`, `PROJET_FRONT`, `PROJET_ENV_TEST` in repos generated before kiln 0.4.)
From the root of the repo (or of the current worktree):
1. `cd $KILN_BACKEND_DIR && set -a && . ../$KILN_TEST_ENV && set +a && uv run python manage.py export_openapi --output ../openapi.json`
2. `cd $KILN_FRONTEND_DIR && pnpm generate:api` (regenerates the frontend types and constraints).
3. Show `git diff --stat openapi.json $KILN_FRONTEND_DIR` and point out added or removed routes.
Commit these files with the backend change: CI fails otherwise.
