New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Dot AI Changelog Fragment

by vfarcic in vfarcic/dot-agent-deck

Create changelog fragment for release notes. An agent skill from vfarcic/dot-agent-deck.

MITAuto-check passedDevelopment

Install Dot AI Changelog Fragment

skills CLI
$ npx skills add vfarcic/dot-agent-deck --skill dot-ai-changelog-fragment -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install vfarcic/dot-agent-deck dot-ai-changelog-fragment --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/vfarcic/dot-agent-deck.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/dot-ai-changelog-fragment .claude/skills/dot-ai-changelog-fragment && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
dot-ai-changelog-fragment
GitHub stars
109
Token cost
~1.4k tokens
SKILL.md length
495 words
Files
1
Skills in repo
23
Repo updated
First seen
Licence
MIT

At a glance

Create changelog fragment for release notes. An agent skill from vfarcic/dot-agent-deck.

  • Works in 5 steps: Identify the PRD → Read the PRD Thoroughly → Determine Fragment Type → …
  • Tasks that involve Changelog and release notes
  • SKILL.md covers Workflow and Guidelines
  • Reaches devopstoolkit.ai

What it does

Dot AI Changelog Fragment is an agent skill from vfarcic/dot-agent-deck. Create changelog fragment for release notes. Invoke during /pr-create workflow during the first push to the PR.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Changelog and release notes. The repository describes itself as: A rich terminal dashboard for monitoring and controlling multiple AI coding agent sessions. The licence is MIT.

When your agent uses it

  • Tasks that involve Changelog and release notes

Example prompts

  • “/dot-ai-changelog-fragment”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Identify the PRD
  2. Read the PRD Thoroughly
  3. Determine Fragment Type
  4. Write the Fragment
  5. Confirm Creation

What it can do on your machine

Read from SKILL.md and the folder at commit 9cc3e60. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • devopstoolkit.ai

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Dot AI Changelog Fragment loads about 1.4k tokens when it runs. Until then it costs about 34 tokens; SKILL.md has 495 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~34
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from vfarcic/dot-agent-deck at commit 9cc3e60, republished under its MIT licence (© vfarcic). 495 words, ~1,364 tokens.

Download SKILL.mdSave it as .claude/skills/dot-ai-changelog-fragment/SKILL.md (or your agent's skills folder).
name
dot-ai-changelog-fragment
description
Create changelog fragment for release notes. Invoke during /pr-create workflow during the first push to the PR.
user-invocable
true

Create Changelog Fragment

Create a towncrier changelog fragment for release notes when completing PRD work. This should be included in the PR so the fragment is reviewed along with the code changes.

Workflow

Step 1: Identify the PRD

If not already known from context, ask: "Which PRD should I create release notes for?"

Look for:

  • PRD mentioned in recent conversation
  • PRD referenced in current branch name (e.g., feature/prd-320-*)
  • PRD file path provided by user
Step 2: Read the PRD Thoroughly

Read the entire PRD file to extract:

  • Problem Statement: What user pain point was solved, why it mattered
  • Solution Overview: What the feature does, how it works
  • User Impact: Specific benefits, what users can now do
  • Key Capabilities: Individual features, options, or modes added
  • Technical Details: Configuration options, environment variables, commands
  • Documentation Updates: Which docs were added or updated (check Milestones section)
Step 3: Determine Fragment Type

Read pyproject.toml to see the available fragment types. Each [[tool.towncrier.type]] section has:

  • A comment above it describing when to use that type
  • A directory field (the type identifier used in the filename, e.g., feature for .feature.md)

First, ask the breaking question — before matching the change to any other type. Determine whether this change is breaking as this project defines it: does it break compatibility with a prior release, or otherwise require existing users to take action to keep working? Read the project's breaking-type comment in pyproject.toml for the project-specific definition — it may be broader than an API/CLI change (for example a wire-protocol, on-disk-format, or other cross-process/compatibility contract, including a change that stays structurally compatible but shifts meaning). When the change matches that definition — or you are unsure and it plausibly could — prefer the breaking type. Under-classifying a breaking change is costly: it ships with the wrong version bump and with no breaking-change entry to warn users.

Otherwise, choose the type that best matches the PRD based on those descriptions.

Show full SKILL.md (179 more words)Show less
Step 4: Write the Fragment

Create file: changelog.d/[issue-id].[type].md

IMPORTANT: Use flat structure, NOT subdirectories!

  • ✅ Correct: changelog.d/329.feature.md
  • ❌ Wrong: changelog.d/feature/329.md

Naming convention:

  • issue-id: GitHub issue number from PRD (e.g., 320)
  • type: Type identifier from step 3 (e.g., feature, bugfix, misc)

Content format:

markdown
## [Feature Title]

[Opening sentence: What this feature is and the problem it solves]

[Key capabilities paragraph: Specific things users can now do, with concrete examples]

[Configuration/usage paragraph if applicable: How to enable or use the feature]

[Documentation link if docs were updated]

Documentation links: If the PRD includes documentation updates, link to the relevant page on devopstoolkit.ai. The URL pattern is:

  • https://devopstoolkit.ai/docs/{project}/{path}
  • Where {project} is: mcp (dot-ai), controller (dot-ai-controller), ui (dot-ai-ui), or stack (dot-ai-stack)
  • And {path} maps from the docs folder (e.g., docs/guides/mcp-recommendation-guide.md → guides/mcp-recommendation-guide)

Example: changelog.d/142.feature.md

markdown
## Multi-Cluster Management

Manage multiple Kubernetes clusters from a single dot-ai instance. Previously, each cluster required its own dot-ai deployment, making it difficult to compare configurations or apply consistent patterns across environments.

The `query` tool now accepts a `--cluster` flag to target specific clusters, and results indicate which cluster each resource belongs to. The `recommend` tool can generate manifests targeting different clusters with environment-specific customizations. Cross-cluster searches let you find resources across all connected clusters simultaneously—useful for tracking down where a particular workload is deployed. Cluster health aggregation shows a unified view of all clusters in the `version` output.

Configure additional clusters by adding kubeconfig contexts to `ADDITIONAL_KUBECONFIGS` (comma-separated paths). Each context becomes available as a cluster target. The default cluster remains the current kubeconfig context when no `--cluster` flag is specified.

See the [Multi-Cluster Setup Guide](https://devopstoolkit.ai/docs/mcp/setup/multi-cluster-setup) for configuration details and examples.
Step 5: Confirm Creation

Show the user:

  1. The fragment file path created
  2. The content written
  3. Reminder to commit and push with the PR

Guidelines

  • User-focused: Describe what users gain, not implementation details
  • Specific: Include concrete examples of what each capability does
  • Complete: Cover all major features added, not just the headline
  • Present tense: "Tools now return..." not "Added support for..."
  • No diary style: "Multi-Cluster Management" not "Added multi-cluster support"
  • Include configuration: Mention environment variables, commands, or setup steps
  • Link to docs: If PRD updated documentation, link to the specific page on devopstoolkit.ai

© vfarcic, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/dot-ai-changelog-fragment of vfarcic/dot-agent-deck.

Open the folder on GitHubat commit 9cc3e60

Compare with similar skills

Dot AI Changelog Fragment next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Dot AI Changelog Fragment compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Dot AI Changelog Fragment this skillvfarcic/dot-agent-deck109—~1.4kAutomated safety check: PassMIT
Simple Englishmoeru-ai/airi50k2 repos~4.6kAutomated safety check: PassMIT
StarRocks Release NotesStarRocks/starrocks12k—~1.9kAutomated safety check: NotesApache-2.0
Cutting A ReleaseTriliumNext/Trilium38k—~3.2kAutomated safety check: PassAGPL-3.0
Rea Changelog Updatemorluto/rea80k—~1.9kAutomated safety check: PassMIT
Mole CLI Release Flowtw93/Mole70k—~2.6kAutomated safety check: PassGPL-3.0

Similar skills

  • Simple English

    moeru-ai/airi

    Write or rewrite technical text with the rules of ASD-STE100 Simplified Technical English so it is clear, unambiguous, and free of AI slop.

    50k GitHub starsUsed in 2 repos~4.6k tokens
    DevelopmentAuto-check passed

  • StarRocks Release Notes

    StarRocks/starrocks

    Drafts English release notes for a StarRocks patch release from the PRs merged into its release branch, then opens a documentation PR and hands translation to /translate.

    12k GitHub stars~1.9k tokensUpdated today
    DevelopmentAuto-check: notes

  • Cutting A Release

    TriliumNext/Trilium

    A skill your agent uses when cutting, preparing, or debugging a Trilium release — bumping the monorepo version, tagging, or diagnosing a failed "Release" workflow run.

    38k GitHub stars~3.2k tokensUpdated today
    DevelopmentAuto-check passed

  • Rea Changelog Update

    morluto/rea

    Prepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.

    80k GitHub stars~1.9k tokensUpdated today
    DevelopmentAuto-check passed

  • Mole CLI Release Flow

    tw93/Mole

    Runbook for assessing and executing a Mole CLI release: distribution channels, pre-flight checks, capital-V tags, build artifacts and the handoff to curated release notes.

    70k GitHub stars~2.6k tokensUpdated today
    DevelopmentAuto-check passed

  • React Router Release Notes Prep

    remix-run/react-router

    Polishes pending React Router change files before the versioning scripts run, and decides whether a long-form What's Changed section is warranted.

    57k GitHub stars~1.1k tokensUpdated yesterday
    DevelopmentAuto-check passed

More from vfarcic/dot-agent-deck

All 24 skills in this repo

  • Dispatch Base

    vfarcic/dot-agent-deck

    Bring the base that every dispatched unit is cut from up to date before the first dot-agent-deck dispatch of a batch in this repo, and check the base dispatch reports afterwards.

    109 GitHub stars~3.1k tokensUpdated today
    Auto-check passed

  • Dispatch Shape

    vfarcic/dot-agent-deck

    Choose the shape of a unit you are about to dispatch in this repo — one agent (--single) or a team (--orchestration '<name') — from divisibility criteria instead of asking, and report the shape you…

    109 GitHub stars~3k tokensUpdated today
    Auto-check passed

  • Docs Screenshots Review

    vfarcic/dot-agent-deck

    Check that a change to the user-facing docs covers both clients (the TUI and the desktop app) unless the feature exists in only one, and decide whether it needs a new or updated screenshot, then…

    109 GitHub stars~1.9k tokensUpdated today
    Auto-check passed

  • Dot AI Request Dot AI Feature

    vfarcic/dot-agent-deck

    Generate a feature request prompt for another dot-ai project.

    109 GitHub stars~679 tokensUpdated today
    Auto-check passed

  • PR Create

    vfarcic/dot-agent-deck

    Take committed work from a branch to a verified pull request — push, open the PR, settle CI and the automated review, answer and resolve every finding, and hand off.

    109 GitHub stars~3.1k tokensUpdated today
    Auto-check passed

  • Publish Docs

    vfarcic/dot-agent-deck

    Publish the docs site to GHCR with a main-<sha tag and bump site/helm/values.yaml so Argo CD picks it up — without cutting a SemVer release.

    109 GitHub stars~1.7k tokensUpdated today
    Auto-check passed

Categories

Questions about Dot AI Changelog Fragment

What does Dot AI Changelog Fragment do?

Create changelog fragment for release notes. An agent skill from vfarcic/dot-agent-deck. Dot AI Changelog Fragment is an agent skill from vfarcic/dot-agent-deck. Create changelog fragment for release notes.

When should I use Dot AI Changelog Fragment?

Dot AI Changelog Fragment fits situations like: tasks that involve Changelog and release notes.

How do I install Dot AI Changelog Fragment in Claude Code?

Run `npx skills add vfarcic/dot-agent-deck --skill dot-ai-changelog-fragment -a claude-code`. Or copy the skill folder (.claude/skills/dot-ai-changelog-fragment in vfarcic/dot-agent-deck) into .claude/skills/dot-ai-changelog-fragment in your project. Claude Code loads it when a task matches its description.

How do I install Dot AI Changelog Fragment in Codex?

Run `npx skills add vfarcic/dot-agent-deck --skill dot-ai-changelog-fragment -a codex`. Or copy the skill folder (.claude/skills/dot-ai-changelog-fragment in vfarcic/dot-agent-deck) into .agents/skills/dot-ai-changelog-fragment in your project. Codex loads it when a task matches its description.

Can I use Dot AI Changelog Fragment in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add vfarcic/dot-agent-deck --skill dot-ai-changelog-fragment -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/dot-ai-changelog-fragment, .gemini/skills/dot-ai-changelog-fragment, .github/skills/dot-ai-changelog-fragment and .opencode/skills/dot-ai-changelog-fragment in your project.

What does Dot AI Changelog Fragment need to run?

SKILL.md names no scripts, command-line tools or credentials: Dot AI Changelog Fragment is instructions for the agent only.

Does Dot AI Changelog Fragment access the network?

SKILL.md names 1 domain. In commands or code: devopstoolkit.ai; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Dot AI Changelog Fragment safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Dot AI Changelog Fragment use?

Dot AI Changelog Fragment is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Dot AI Changelog Fragment use?

About 1.4k tokens (SKILL.md is roughly 5.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Dot AI Changelog Fragment?

Skills that share tags, products or a category with Dot AI Changelog Fragment: Simple English (moeru-ai/airi, 50k stars), StarRocks Release Notes (StarRocks/starrocks, 12k stars), Cutting A Release (TriliumNext/Trilium, 38k stars) and Rea Changelog Update (morluto/rea, 80k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Dot AI Changelog Fragment?

vfarcic (a GitHub user) maintains it in vfarcic/dot-agent-deck, which has 109 GitHub stars. The repository holds 23 skills in this directory. The repository was last updated on October 10, 2026.

Source: vfarcic/dot-agent-deck on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.