Loading...
Loading...
Found 8 Skills
Read this skill before updating changelogs
Clawdbot documentation expert with decision tree navigation, search scripts, doc fetching, version tracking, and config snippets for all Clawdbot features
Create changelog files for important commits in a PR
Adds documents to golden dataset with validation. Use when curating test data or saving examples.
Write and maintain a CHANGELOG that records every completed code change without becoming a commit dump. Use after any code change in a project that has a changelog, when setting one up, when preparing a release, or when the user asks why something was built this way. Keep mechanical entries brief; preserve reasons and rejected alternatives for non-obvious decisions. Do not use for commit messages, PR descriptions, or user-facing release notes.
Enterprise template management with code boilerplates, feedback templates, and project optimization workflows
This skill should be used when the user asks about new features, recent changes, or updates in Claude Code — for example "what's new in Claude Code?", "Claude Code changelog", "what did I miss in Claude?", "any recent updates?", "tell me about new Claude features", or "what's changed since version 1.0.30?". It fetches the official changelog, filters for notable features (excluding bug fixes), researches each feature for deeper context on Anthropic's website, and presents mini-article summaries. Supports both automatic tracking (since last check) and explicit version queries.
Version-pinned inventory of the telemetry (spans, metrics, logs, attributes) emitted by OpenTelemetry collector components and SDK instrumentation packages. Use when working with a covered component — what it emits at a given version, or how emission changed across versions — and when upgrading a component or SDK version, to see the telemetry after the change.