# bugfix-changelog

> This skill should be used when the user asks to 'generate changelog', 'create changelog entry', 'update changelog for bugfix', or needs to document a completed bug fix in the changelog.

- Author: Ngoc
- Repository: Vegarnom/mega-team-v4
- Version: 20260202115326
- Stars: 0
- Forks: 0
- Last Updated: 2026-02-06
- Source: https://github.com/Vegarnom/mega-team-v4
- Web: https://mule.run/skillshub/@@Vegarnom/mega-team-v4~bugfix-changelog:20260202115326

---

---
name: bugfix-changelog
description: This skill should be used when the user asks to 'generate changelog', 'create changelog entry', 'update changelog for bugfix', or needs to document a completed bug fix in the changelog.
allowed-tools: Read, Bash, Glob, Grep
version: 1.0
---

# Bugfix Changelog Generator v1.0

Generate changelog entry cho bugfix hoàn thành.

---

## USAGE

```bash
/bugfix-changelog                  # Generate from current changes
/bugfix-changelog plan-fix-123.md  # From specific plan
```

---

## WORKFLOW

### Step 1: Gather Information

```bash
# Get plan file
PLAN_FILE=$(ls plan-fix-*.md 2>/dev/null | head -1)

# Get issue ID
ISSUE_ID=$(git branch --show-current | grep -oE '[0-9]+')

# Get commit messages
git log --oneline HEAD~3..HEAD
```

### Step 2: Generate Changelog Entry

```markdown
### Fixed

- **{Module/Component}:** {Short description of fix} (#{issue_id})
  - Root cause: {brief root cause}
  - Impact: {who was affected}
```

### Step 3: Categorize

```
Categories:
- Fixed: Bug fixes
- Security: Security-related fixes
- Performance: Performance improvements
- Deprecated: Deprecated features
```

---

## OUTPUT FORMAT

### Keep a Changelog Format

```markdown
## [Unreleased]

### Fixed

- **Auth:** Fix login failing with 500 error when user has no profile (#123)
  - Root cause: Null check missing for optional profile
  - Impact: Users without profile could not login
```

### Conventional Changelog Format

```markdown
### Bug Fixes

- **auth:** fix login error for users without profile ([#123](link))
```

---

## CHANGELOG RULES

1. **BE concise** - One line summary
2. **INCLUDE issue** - Link to issue/PR
3. **MENTION impact** - Who was affected
4. **CATEGORIZE correctly** - Fixed/Security/etc