technical-docs
Installation
SKILL.md
Technical Documentation Writing
Core Principles
1. Lead with "Why", Then "How"
Every section must answer: Why would a developer need this?
Bad:
## Server Actions
Use `captureException` in Server Actions to report errors.
Good:
## Server Actions
Server Actions that return error states to the client catch errors before Sentry sees them.
Report these manually so you don't lose visibility.
Related skills
More from getsentry/sentry-docs
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.
1create-branch
Create a git branch following Sentry naming conventions. Use when asked to "create a branch", "new branch", "start a branch", "make a branch", "switch to a new branch", or when starting new work on the default branch.
1docs-review
Review documentation for Sentry style and voice. Use when reviewing or writing user-facing documentation to ensure it follows the Sentry documentation style guide.
1