agentsclimarketplace

Wiki changelog

Skill Pyfagorass/bookofspells/skills/microsoft/wiki-changelog

📖 The Book of Spells: a curated, enchanted index of real LLM tooling — and a pipeline that gathers SKILL.md skills from many houses into one searchable shelf.

Install
npx -y skills add Pyfagorass/bookofspells --skill wiki-changelog

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Analyzes git commit history and generates structured changelogs categorized by change type. Use when the user asks about recent changes, wants a changelog, or needs to understand what changed in the repository.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.8 KB, as published. Nobody here has run it

Wiki Changelog

Generate structured changelogs from git history.

Source Repository Resolution (MUST DO FIRST)

Before generating any changelog, you MUST determine the source repository context:

  1. Check for git remote: Run git remote get-url origin to detect if a remote exists
  2. Ask the user: "Is this a local-only repository, or do you have a source repository URL (e.g., GitHub, Azure DevOps)?"
    • Remote URL provided → store as REPO_URL, use linked citations for commit hashes and file references
    • Local-only → use plain commit hashes and file references
  3. Do NOT proceed until source repo context is resolved

When to Activate

  • User asks "what changed recently", "generate a changelog", "summarize commits"
  • User wants to understand recent development activity

Procedure

  1. Examine git log (commits, dates, authors, messages)
  2. Group by time period: daily (last 7 days), weekly (older)
  3. Classify each commit: Features (🆕), Fixes (🐛), Refactoring (🔄), Docs (📝), Config (🔧), Dependencies (📦), Breaking (⚠️)
  4. Generate concise user-facing descriptions using project terminology

Constraints

  • Focus on user-facing changes
  • Merge related commits into coherent descriptions
  • Use project terminology from README
  • Highlight breaking changes prominently with migration notes
  • When REPO_URL is available, link commit hashes: [abc1234](REPO_URL/commit/abc1234) and changed files: [file_path](REPO_URL/blob/BRANCH/file_path)

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.