Your task: analyze the PR and create/update MoonShine documentation.
Critical Rules
[!WARNING]
DO NOT FABRICATE! If you are uncertain about something or lack information:
Search for information in .context/moonshine (MoonShine codebase)
Use WebSearch/WebFetch to find current information
Ask the user via AskUserQuestion
Step-by-Step Plan
Retrieve PR Information
Use gh pr view $ARGUMENTS to get PR details
Study changes in the PR via gh pr diff $ARGUMENTS
Understand the context: is it a new feature, enhancement, or fix?
Create Git Branch
Based on the PR content, determine the section name (e.g., "rating-component", "new-field-type", etc.)
Create a new git branch with a descriptive name: git checkout -b docs/section-name
Use kebab-case for branch naming
Branch name should reflect the documentation section being created/updated
Study Documentation Formatting Rules
Read the file references/formatting-rules.md
This is a mandatory file with formatting and structure rules
Follow all rules from there
Determine Type of Change
Is this a new documentation section or an update to existing one?
If uncertain — check existing structure in ru/ and en/ directories
Use Grep/Glob to search for similar sections if needed
Create/Update Russian Version (ru/)
ALWAYS start with the Russian version in the ru/ directory
Follow the structure from references/formatting-rules.md
Translate to English (en/)
After completing the Russian version, create an English translation
Place in en/ following the same path as in ru/
Synchronize line-by-line with the Russian version where possible
Preserve all formatting and structure
Update Navigation (if new section)
If this is a new section, add it to the navigation.md file
Check which section it logically belongs to
Quality Check
Are all code examples correct?
Are there screenshots (if needed)?
Do all links use the {{version}} placeholder?
Are RU and EN versions synchronized?
If Questions Arise
Check .context/moonshine to clarify implementation details
Use WebSearch to find additional information
Ask the user via AskUserQuestion
Start working!
1---2name: doc-pr3description: Generate documentation by PR link or PR ID4---56User provided Pull Request URL or ID: $ARGUMENTS78## MoonShine Codebase Context910!`git -C .context/moonshine pull 2>/dev/null`1112Your task: analyze the PR and create/update MoonShine documentation.1314## Critical Rules1516> [!WARNING]17> **DO NOT FABRICATE!** If you are uncertain about something or lack information:18> 1. Search for information in `.context/moonshine` (MoonShine codebase)19> 2. Use WebSearch/WebFetch to find current information20> 3. Ask the user via AskUserQuestion2122## Step-by-Step Plan23241. **Retrieve PR Information**25 - Use `gh pr view $ARGUMENTS` to get PR details26 - Study changes in the PR via `gh pr diff $ARGUMENTS`27 - Understand the context: is it a new feature, enhancement, or fix?28292. **Create Git Branch**30 - Based on the PR content, determine the section name (e.g., "rating-component", "new-field-type", etc.)31 - Create a new git branch with a descriptive name: `git checkout -b docs/section-name`32 - Use kebab-case for branch naming33 - Branch name should reflect the documentation section being created/updated34353. **Study Documentation Formatting Rules**36 - Read the file [references/formatting-rules.md](references/formatting-rules.md)37 - This is a mandatory file with formatting and structure rules38 - Follow all rules from there39404. **Determine Type of Change**41 - Is this a new documentation section or an update to existing one?42 - If uncertain — check existing structure in `ru/` and `en/` directories43 - Use Grep/Glob to search for similar sections if needed44455. **Create/Update Russian Version (ru/)**46 - ALWAYS start with the Russian version in the `ru/` directory47 - Follow the structure from references/formatting-rules.md48496. **Translate to English (en/)**50 - After completing the Russian version, create an English translation51 - Place in `en/` following the same path as in `ru/`52 - Synchronize line-by-line with the Russian version where possible53 - Preserve all formatting and structure54557. **Update Navigation (if new section)**56 - If this is a new section, add it to the `navigation.md` file57 - Check which section it logically belongs to58598. **Quality Check**60 - Are all code examples correct?61 - Are there screenshots (if needed)?62 - Do all links use the `{{version}}` placeholder?63 - Are RU and EN versions synchronized?6465## If Questions Arise66671. Check `.context/moonshine` to clarify implementation details682. Use WebSearch to find additional information693. Ask the user via AskUserQuestion7071Start working!
Run npx skillmds@latest add moonshine-software/doc-pr in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
Generate documentation by PR link or PR ID It is listed under Docs & Writing on SkillMD.
This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
moonshine-software (@moonshine-software) published this skill. Their other Agent Skills are listed on their SkillMD profile.