THE FIRST LESSONপ্রথম পাঠ
# Create the skill directory and file mkdir -p .claude/skills/migration-check touch .claude/skills/migration-check/SKILL.md
/migration-check. Keep it a single, clear job.কেবাব-কেস নাম = স্কিলের পরিচয়। এটাই স্ল্যাশ কমান্ড হবে: /migration-check। একটাই স্পষ্ট কাজ রাখো।description field is the trigger. Pack it with the words a user would actually say to invoke this skill.description ফিল্ডই ট্রিগার। এতে সেই শব্দগুলো ভরো যা কোনো ব্যবহারকারী এই স্কিল ডাকতে আসলে বলবে।--- name: migration-check description: > Run the pre-release database migration check. Use when asked to "check migrations before release", "verify db migrations", "pre-release db check", or "migration sign-off". ---
--- name: migration-check description: > Checks migrations. ---
## Steps 1. Run `python manage.py showmigrations --list` and collect every unapplied migration. 2. For each unapplied migration, open the file and verify: - No column drop without a safe default - No table rename without an alias period - All new NOT NULL columns have a DB-level default 3. Execute `python manage.py migrate --run-syncdb --dry-run` and confirm exit code 0. 4. Run `python manage.py migrate --fake-initial --dry-run` to simulate rollback path. Confirm no errors. 5. Output a sign-off block: ``` Migration Check — PASS/FAIL Checked: <date> Unapplied: <N> Risk: LOW | MEDIUM | HIGH Notes: … ```
--- name: release-notes description: > Generate release notes or a CHANGELOG entry for the current release. Use when asked to "generate release notes", "write changelog", "create CHANGELOG entry", "summarise what changed since last tag", or "draft release notes for vX.Y.Z". Gathers merged PRs since the last git tag, groups them by type, and writes a formatted Markdown block. ---
## Steps 1. Find the last git tag: `git describe --tags --abbrev=0` 2. List all merge commits since that tag: `git log <tag>..HEAD --merges --oneline` 3. For each merge commit, extract the PR title and number. Group by conventional-commit prefix: - `feat:` → ✨ Features - `fix:` → 🐛 Bug Fixes - `docs:` → 📝 Documentation - `chore:` / other → 🔧 Maintenance 4. Write a Markdown CHANGELOG block in this format: ``` ## [vX.Y.Z] — YYYY-MM-DD ### ✨ Features - PR #123 — Add payment retry logic ### 🐛 Bug Fixes - PR #118 — Fix null pointer in OrderService ### 🔧 Maintenance - PR #115 — Bump dependencies ``` 5. Ask: "Should I append this to CHANGELOG.md?" and wait for confirmation before writing to disk.
## Example Output section at the end of the body. One concrete example eliminates most ambiguity.
সমাধান: বডির শেষে ## Example Output বিভাগ যোগ করো। একটা কংক্রিট উদাহরণ বেশিরভাগ অস্পষ্টতা দূর করে।
.claude/skills/<name>/SKILL.md. Drop it anywhere else and Claude won't find it.
স্কিল অবশ্যই .claude/skills/<name>/SKILL.md-তে থাকতে হবে। অন্য কোথাও রাখলে Claude খুঁজে পাবে না।
--- name: release-notes # ← kebab-case, becomes /release-notes description: > Generate release notes or a # ← trigger phrases users would say CHANGELOG entry. Use when asked to "write changelog", "release notes for vX.Y.Z", "summarise since last tag". --- ## Steps # ← numbered, imperative 1. Identify the last git tag … 2. List merge commits since tag … 3. Group by conventional prefix … 4. Write formatted Markdown block … 5. Confirm before writing to disk … ## Example Output # ← concrete template (optional but powerful) ## [v1.4.0] — 2026-06-20 ### ✨ Features - PR #42 — Add skill authoring guide ### 🐛 Bug Fixes - PR #41 — Fix trigger on bilingual decks
.claude/skills/ is available to every developer on the team — not just the person who wrote it..claude/skills/-এ কমিট করা একটি স্কিল টিমের প্রতিটি ডেভেলপারের কাছে পাওয়া যায় — শুধু যে লিখেছে তার কাছে নয়।