mcp-release-notes
Draft MongoDB MCP Server release notes for a new version by fetching the corresponding release from mongodb-js/mongodb-mcp-server and formatting them for the docs. Use when asked to draft or create MCP Server release notes.
소스 정보
- 저장소
- mongodb/docs
- 최근 소스 활동
- 2026년 9월 17일 22:55
- 감지된 SKILL.md 언어
- 영어
- 스타
- 777
- 포크
- 1,699
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
파일 탐색기
2 개 파일SKILL.md 표시 중
SKILL.md
소스 지침 · 읽기 전용 미리보기- name
- mcp-release-notes
- internal
- true
- description
- Draft MongoDB MCP Server release notes for a new version by fetching the corresponding release from mongodb-js/mongodb-mcp-server and formatting them for the docs. Use when asked to draft or create MCP Server release notes.
- allowed-tools
- Read, Grep, Glob, Agent, Edit
- argument-hint
- [version] e.g. 1.9.0
# Draft MCP Server Release Notes for $ARGUMENTS
Follow the workflow defined in `.claude/skills/release-notes-base/SKILL.md`, substituting the following values:
| Placeholder | Value |
|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| `{VERSION}` | `$ARGUMENTS` |
| `{GITHUB_REPO}` | `mongodb-js/mongodb-mcp-server` |
| `{RELEASE_NOTES_FILE}` | `content/mcp-server/source/release-notes.txt` |
| `{PRODUCT_SUBSTITUTION}` | bare version number only (e.g. `1.9.0`) — no substitution constant, no `v` prefix |
| `{VERSION_KEY}` | N/A — `content/mcp-server/snooty.toml` has no version key; skip step 6 |
| `{SNOOTY_TOML}` | N/A |
| `{CHANGELOG_LINK}` | Multi-line inline RST hyperlink — see format overrides below for the exact format |
## Format overrides
These rules override the shared defaults in `release-notes-base`. For RST
formatting (heading style, changelog link), read `references/rst-formatting.md`.
- **Section labels:** before drafting, ask the writer which section labels to use. Present the following options and allow free input:
- `New features and updates:`
- `Bug Fixes:`
- A custom label the writer provides
- Omit a section entirely if it has no entries. If the release has both new features and bug fixes, confirm whether to use both sections or combine them under a single label.
GitHub에서 보기