document-api-endpoint vs commit
Side-by-side comparison of two Claude Agent Skills. Pick the right one for Claude Code or Claude Desktop.
Document and type a Sentry API endpoint. Write or fix @extend_schema decorators, specify response TypedDicts, type request parameters, correct type drift betwee
Comparison
| Feature | document-api-endpoint | commit |
|---|---|---|
| Bundled scripts | no | no |
| Allowed tools | any | any |
| Install scope | personal | personal |
| Category | documents | coding |
| Verified | ||
| License | — | — |
| Author | Sentry | Sentry |
| Repo | getsentry/skills | getsentry/skills |
When to pick document-api-endpoint
Document and type a Sentry API endpoint. Write or fix @extend_schema decorators, specify response TypedDicts, type request parameters, correct type drift between the declared schema and the runtime response, and validate the generated spec. Use when asked to "document an endpoint", "add OpenAPI docs", "add/fix @extend_schema", "type an endpoint response", "fix the response type", "fix type drift", "reuse a response type", "split an overloaded endpoint", "specify the response schema", "add a TypedDict response", "migrate a legacy api-docs path", "fix a parameter type", or "make an endpoint public" / "promote an endpoint" (promotion is one section here).
When to pick commit
ALWAYS use this skill when committing code changes — never commit directly without it. Creates commits following Sentry conventions with proper conventional commit format and issue references. Trigger on any commit, git commit, save changes, or commit message task.
Looking for something else? Browse all skills.