Update to AI DevKit

{
  "description": "AI DevKit · Update CHANGELOG.md Unreleased items from git commits since the latest release. Use when users ask to update changelog/release notes from recent commits, with one concise line per commit and commit/PR links.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 301
    }
  ],
  "name": "changelog",
  "skill_md_contents": "---\nname: changelog\ndescription: AI DevKit · Update CHANGELOG.md Unreleased items from git commits since the latest release. Use when users ask to update changelog/release notes from recent commits, with one concise line per commit and commit/PR links.\n---\n\n# Changelog\n\nUpdate the top `Unreleased` list in `CHANGELOG.md` from commits after the latest release.\n\n## Workflow\n\n1. Find the latest release base:\n   - Prefer the latest reachable tag: `git describe --tags --abbrev=0`.\n   - If there are no tags, search recent history for a release commit and use that hash.\n2. Get commits: `git log <base>..HEAD --reverse --format='%H%x09%s'`.\n3. Derive the GitHub repo URL from `git remote get-url origin`.\n4. For each commit, add one concise changelog line:\n   - Format: `- [<short-hash>](<url>) <one-line summary>`\n   - If the commit clearly relates to a PR, link the hash to the PR URL instead of the commit URL.\n   - Detect PRs from subjects like `(#123)`, merge commits, or `gh pr list --search <hash> --state all --json number,url`.\n5. Insert the new lines into the top `Unreleased` section/list in `CHANGELOG.md`.\n   - If no `Unreleased` section exists, create one at the top.\n   - Do not create a dated release heading unless the user asks for a release.\n\n## Rules\n\n- Keep one line per commit.\n- Preserve the existing changelog style when obvious.\n- Always add entries to the top `Unreleased` list.\n- Skip noisy commits only when clearly non-user-facing and explain what was skipped.\n- Do not invent PR links; use commit links when PR evidence is missing.\n"
}