Add techtenstein.com/slug-forge

[sathvic-kollu]

Adding slug-forge API — Turn any Unicode string into a clean, URL-safe slug.

Live: https://slug-forge.techtenstein.com
OpenAPI: https://slug-forge.techtenstein.com/openapi.json

[gemini-code-assist]

Code Review

This pull request introduces the initial OpenAPI 3.1.0 specification for the slug-forge API, defining endpoints for landing, health checks, OpenAPI specs, single slug generation, and batch slug generation. Feedback on the specification highlights several improvements: adding missing response definitions for the root, health, and openapi.json endpoints to comply with the OpenAPI standard; correcting YAML boolean syntax from 'True' to 'true'; typing the 'lower' and 'strict' query parameters as booleans instead of strings; and defining response content schemas for the slug and batch endpoints to facilitate better client SDK generation.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

The OpenAPI specification requires that every operation object contains a responses field. Please add a response definition for this endpoint.

    get:
      summary: "Landing / docs"
      responses:
        200:
          description: "Success"

[gemini-code-assist]

The OpenAPI specification requires that every operation object contains a responses field. Please add a response definition for the /health endpoint.

    get:
      summary: "Health"
      responses:
        200:
          description: "Success"

[gemini-code-assist]

The OpenAPI specification requires that every operation object contains a responses field. Please add a response definition for the /openapi.json endpoint.

    get:
      summary: "OpenAPI spec"
      responses:
        200:
          description: "Success"

[gemini-code-assist]

In YAML and OpenAPI, boolean values should be lowercase true or false to ensure compatibility with all parsers and validators.

          required: true

[gemini-code-assist]

The lower and strict parameters represent boolean flags. They should be typed as boolean with boolean defaults (true/false) instead of string to improve type safety and client generation.

        - name: "lower"
          in: "query"
          schema:
            type: "boolean"
            default: true
        - name: "strict"
          in: "query"
          schema:
            type: "boolean"
            default: false

[gemini-code-assist]

It is highly recommended to define the response content (e.g., application/json or text/plain) so that client SDK generators can correctly type the response.

      responses:
        200:
          description: "Slug result"
          content:
            text/plain:
              schema:
                type: "string"

[gemini-code-assist]

In YAML and OpenAPI, boolean values should be lowercase true or false to ensure compatibility with all parsers and validators.

          required: true

[gemini-code-assist]

Defining the response content schema (e.g., an array of strings in JSON) is recommended so that client generators can produce typed models.

      responses:
        200:
          description: "Array of slugs"
          content:
            application/json:
              schema:
                type: "array"
                items:
                  type: "string"