release-notes
Skill by newton-physics · updated · ★ 5.8k
Use when drafting or reviewing Newton GitHub Release notes, release announcements, or high-level release summaries for patch, minor, RC, or final releases. release-notes is published by newton-physics on GitHub.
Last commit in the past day
Apache-2.0: permissive, fine for commercial use
Clear description, installs from GitHub, 5,813 stars, original repository
Not checked yet. What we check
Install release-notes
Built from the published package, never by AIgit clone --depth 1 https://github.com/newton-physics/newton /tmp/newton && mkdir -p ~/.claude/skills && cp -r /tmp/newton/.claude/skills/release-notes ~/.claude/skills/release-notesRun in your terminal. Claude Code loads skills from ~/.claude/skills automatically.
git clone --depth 1 https://github.com/newton-physics/newton /tmp/newton && mkdir -p ~/.gemini/antigravity-cli/skills && cp -r /tmp/newton/.claude/skills/release-notes ~/.gemini/antigravity-cli/skills/release-notesAntigravity CLI loads skills from ~/.gemini/antigravity-cli/skills, or .agents/skills for one project.
Skills can run scripts on your machine. Some need an API key: check the README.
Alternatives to release-notes
All alternatives →Handle quick, repeatable Dagger repository maintenance chores. Use when the user asks for small operational changes and wants the same established edits and commit style applied quickly.
Use when asked to fix short descriptions of Python type members.
Use when generated code looks wrong, code generation fails, or you need to understand FRB internals
Perform a structured code review of changes, checking for correctness, style, tests, and potential issues.
Detect and fix clang-format, clang-tidy, and copyright header violations in an OpenVINO C++ codebase. Use when the user complains about code style or formatting, asks to clean up changes, fix linting, add a copyright header, or when a style check or linting CI job is failing. Do not use for build errors, compilation failures, linker errors, test failures, runtime crashes, accuracy issues, or CMake config problems.
Use when deciding whether make bazel_prepare is required before build or test commands based on local file changes in TiDB.
release-notes: common questions
How do I install release-notes?
Run the command above to copy the skill into ~/.claude/skills/. Claude Code picks it up automatically.
Is release-notes free?
The code is published under the Apache-2.0 licence. The service it connects to may have its own pricing.
Is release-notes safe to use?
It scores 82 of 100. Grades: maintenance A, licence A, quality A. The security check has not run for it yet. Review the code before you install. How grades work.
What are alternatives to release-notes?
Similar skills: dagger-chores, fix-members-short-description, frb-debugging, code-review.
