agentleFS
jamiebrynes7jamiebrynes7/obsidian-todoist-plugin/.claude/skills/write-changelog/SKILL.md

write-changelog

Skill1.2k starsChanged 10 months agoMITView on GitHub

Write or update changelog entries with user-focused language

13 other projects use a version of this.

Trending

Quiet since May.thin dataabout the whole repository

Dec 2025: 0 mentionsJan 2026: 1 mentionFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 1 mentionJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the jamiebrynes7/obsidian-todoist-plugin repository that our weekly crawl found: only 4 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Most recently taken up by

Used with

Projects with it also use security-audit.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • CloudflareSkill

    security-audit

    Security guidance and vulnerability review for codebases, APIs, services, CLI tools, libraries, and daemons. Use for security questions, focused reviews, vulnerability research, security audits, or pen tests. Run the complete workflow only for explicit codebase audit or pen-test requests, full/comprehensive/end-to-end reviews, or requested report artifacts.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 13 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write or update changelog entries following these guidelines:

    line 8
  2. Very specific:

    Always add new entries to the ## Unreleased section at the top of the changelog.

    line 31

“Common” is measured: kept by at least 6 in 10 of the 13 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Changelog

Write or update changelog entries following these guidelines:

Guidelines

  • Focus on user benefits rather than implementation details
  • Keep entries concise - typically a single line without subpoints
  • Emphasize what the user can now do or how their experience improves
  • Avoid technical specifics like state management, CSS classes, or internal architecture

Categories

Entries are organized under these category headings:

  • ### ✨ Features - New functionality for users
  • ### 🐛 Bug Fixes - Corrections to existing behavior
  • ### 🔁 Changes - Modifications to existing features
  • ### ⚙ Internal - Technical changes (use sparingly, still user-focused)
  • ### 🌐 Translations - New or updated translations
  • ### Breaking changes - For major releases only
  • ### Deprecated - Features being phased out

Unreleased Section

Always add new entries to the ## Unreleased section at the top of the changelog. Create the appropriate category heading if it doesn't exist yet. Entries are moved to a versioned section during the release process.

Examples

Good:

  • "Added keyboard shortcuts for common actions"
  • "Tasks now sync automatically when Obsidian starts"
  • "Fixed tasks not appearing after editing"

Bad:

  • "Refactored TaskStore to use Redux pattern with selectors"
  • "Added useEffect hook to trigger sync on mount"
  • "Fixed CSS specificity issue in task-list component"

Location

The changelog is located at docs/docs/changelog.md.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.