authorization-doc-review
Ensures authorization documentation stays aligned with backend and frontend implementation.
Install
mkdir -p .claude/skills/authorization-doc-review-nicobit && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/15909" && unzip -o skill.zip -d .claude/skills/authorization-doc-review-nicobit && rm skill.zipInstalls to .claude/skills/authorization-doc-review-nicobit
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Review and update authorization documentation when roles, route protection, permissions, or module access behavior change across frontend, backend, and specs.Key capabilities
- →Identify changed modules or routes
- →Classify affected surfaces
- →Verify frontend and backend enforcement
- →Update access control matrix
How it works
The skill guides a review process to ensure authorization documentation aligns with implementation across frontend, backend, and specifications.
Inputs & outputs
When to use authorization-doc-review
- →Update access control matrix
- →Review module authorization
- →Sync auth docs with code
- →Verify route guards
About this skill
name: authorization-doc-review description: Review and update authorization documentation when roles, route protection, permissions, or module access behavior change across frontend, backend, and specs.
Authorization Documentation Review
Use this skill when a change touches roles, route protection, permissions, or module access behavior.
Goal
Keep authorization documentation aligned with implementation across:
- frontend route guards
- backend auth dependencies and role checks
- feature specs
- API specs
- test plans
- central authorization docs
Read First
docs/standards/security/access-control-matrix.mddocs/standards/security/module-authorization.mdfrontend/src/auth/useAuthZ.tsxbackend/app/auth/roles.pybackend/shared/authz.py
Checklist
- Identify every changed module, route, page, or endpoint.
- Classify each affected surface as:
- public
- authenticated
- role-restricted
- Verify frontend and backend enforcement stay aligned.
- Update:
docs/standards/security/access-control-matrix.mdif role meaning changeddocs/standards/security/module-authorization.mdfor affected modules- feature spec / API spec / test plan if the change is feature-scoped
- Ensure tests cover both allowed and denied paths where relevant.
Output
When using this skill, provide:
- affected modules and routes
- required documentation updates
- any mismatches between code and docs
- any missing auth tests
When not to use it
- →When no changes to roles, route protection, permissions, or module access behavior have occurred
Limitations
- →Applies only when roles, route protection, permissions, or module access behavior change
How it compares
This skill provides a structured checklist for auditing authorization documentation, unlike manually tracking changes across systems.
Compared to similar skills
authorization-doc-review side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| authorization-doc-review (this skill) | 0 | 4mo | No flags | Intermediate |
| rsyslog-doc | 1 | 2mo | No flags | Beginner |
| authorization-doc-review | 0 | 4mo | No flags | Intermediate |
| writing-a-malware-analysis-report | 0 | 1mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by nicobit
View all by nicobit →You might also like
rsyslog-doc
rsyslog
Guidelines for maintaining structured, RAG-optimized documentation and module metadata.
authorization-doc-review
nicobit
Review and update authorization documentation when roles, route protection, permissions, or module access behavior change across frontend, backend, and specs.
writing-a-malware-analysis-report
meltedinhex
Structures a clear, actionable malware analysis report covering summary,
cookbook-audit
anthropics
Audit an Anthropic Cookbook notebook based on a rubric. Use whenever a notebook review or audit is requested.
security-requirement-extraction
wshobson
Derive security requirements from threat models and business context. Use when translating threats into actionable requirements, creating security user stories, or building security test cases.
code-review-checklist
vudovn
Code review guidelines covering code quality, security, and best practices.