aist-api-review

Review REST API endpoints for isolation, permissions, and serializer usage.

Updated Aug 31, 2025
One-click install
npx skills add https://github.com/aist-ai-sast/aist --skill aist-api-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aist-api-review
Source: https://github.com/aist-ai-sast/aist/tree/main/.claude/skills/aist-api-review
Command: npx skills add https://github.com/aist-ai-sast/aist --skill aist-api-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines the process of validating new or modified REST API endpoints for organization isolation, permission correctness, and proper serializer usage, reducing risk in deployments.

Core Features & Use Cases

  • Endpoint isolation checks: verifies tenant isolation and access boundaries across services.
  • Permission and serializer review: assesses permission classes, view-level checks, and serializer field usage for safety.
  • Superuser bypass detection: identifies and mitigates risky admin-endpoint bypass scenarios.
  • Use Case: When adding or updating endpoints in aist/api/, run a comprehensive review to surface design and security gaps before merge.

Quick Start

Inspect the aist/api/ codebase and generate a structured API-review report focused on isolation, permissions, and serializer usage.

Frequently Asked Questions about aist-api-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review REST API endpoints for organization isolation and RBAC permissions?

Reviewing REST API endpoints for organization isolation and RBAC involves verifying permission classes, view-level checks, and tenant access boundaries. This structured assessment ensures endpoints enforce proper access controls and align with security policies before deployment.

What is superuser bypass detection in API security reviews?

Superuser bypass detection in API security reviews identifies and mitigates risky admin-endpoint bypass scenarios. It verifies that superuser controls do not unintentionally circumvent organization isolation, RBAC permissions, or tenant access boundaries.

How do I check serializer field usage for safety during a code review?

Checking serializer field usage for safety involves assessing how serializers expose data through REST API endpoints. You must verify that sensitive fields are properly restricted and align with organization isolation and permission policies.

When do I need to run a comprehensive REST API security review?

You need to run a comprehensive REST API security review when adding or updating endpoints in your codebase. It surfaces design and security gaps, such as tenant isolation failures or incorrect permissions, before merging new or modified code.

Does this API review process work for endpoints outside of the aist/api/ directory?

This API review process is specifically applied during the integration of new or modified endpoints in aist/api/. While its structured criteria for security, design, and compliance can conceptually evaluate other REST APIs, its core logic targets the aist/api/ codebase.