What problem does it solve? Code changes to views, API endpoints, forms, or roles can silently open access to resources that should be restricted, and reading the code alone rarely proves the boundary holds. This Skill enforces a systematic access-control review that proves every boundary with a negative test rather than an assumption. ## Core Features & Use Cases - Resource-Role-Action Matrix: Builds a table of who can do what across roles (anonymous, student, tutor, parent, admin) and flags cells where permission exists without a code check. - Ownership and Queryset Audits: Verifies owners come from request.user rather than client data, and that object lookups filter by owner instead of bare primary keys. - Mandatory Negative Tests: Requires a test proving an outsider gets 403 or 404 for every boundary, such as another tutor accessing a student of a different tutor. - Use Case: After adding a new endpoint that returns a student's submission, run this review to confirm the queryset is filtered by the requesting tutor, the decorator is in place, and a test proves another tutor receives 403. ## Quick Start Review the access boundaries of the views and endpoints I just changed and confirm each one is covered by a negative permission test.
