wiki-changelog

原文涵盖的主题

• Wiki Changelog
• Source Repository Resolution (MUST DO FIRST)
• When to Activate
• Procedure
• Constraints

Generate structured changelogs from git history. 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 REPOURL, 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 User asks "what changed recently", "generate a changelog", "summarize commits" User wants to understand recent development activity 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 Focus on user-facing changes Merge related commits into coherent descriptions Use project terminology from README Highlight breaking changes prominently with migration notes When REPOURL is available, link

这里只展示节选，请以完整原文和当前要求为准。