القائمة
Fill changelog entries for the current branch. Use when the user asks to fill changelog, write changelog entries, update changelog, or prepare changelog for a PR.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Add a REST endpoint to the app — type contract in common, validation schema, action implementation, registration, tests, changelog. Use when the user asks to add/expose/create a new endpoint, route, REST API, or wants to convert a function into an HTTP-callable action. Branches between custom actions and DataSet-backed CRUD.
Review all changes on the current branch. Use when the user asks for a code review or PR review.
Wire a new entity into the data layer — model, store binding, DataSet with authorization/hooks, optional entity sync. Use when the user asks to add an entity, persist a model, expose a collection, or set up a new DataSet.
| name | fill-changelog |
| description | Fill changelog entries for the current branch. Use when the user asks to fill changelog, write changelog entries, update changelog, or prepare changelog for a PR. |
Automate filling changelog entries based on the changes in the current branch.
Version bumps MUST be configured before running this skill. If yarn version check fails, version files need to be adjusted first using yarn version patch/minor/major or yarn bumpVersions (interactive).
Run yarn version check to validate version manifests exist:
yarn version check
If fails: Stop and report error. The user must run yarn version patch, yarn version minor, yarn version major, or yarn bumpVersions first to configure version bumps.
Run with force flag to ensure all drafts are created or recreated:
yarn changelog create -f
This creates files in .yarn/changelogs/ with the pattern {package-name}.{manifest-id}.md.
Gather information about changes:
git diff master...HEAD --stat
git log master...HEAD --oneline
Read the changed files to understand what was actually modified.
Use Glob to find .yarn/changelogs/*.md files, then Read to load their content.
Map changes to the appropriate sections and fill the changelog drafts.
| Section | When to Use |
|---|---|
| ✨ Features | New functionality, new files, new capabilities |
| 🐛 Bug Fixes | Corrections to existing behavior |
| 📚 Documentation | README, comments, documentation files |
| ⚡ Performance | Optimizations |
| ♻️ Refactoring | Code restructuring without behavior change |
| 🧪 Tests | Test additions/modifications |
| 📦 Build | Build system, dependencies configuration |
| 👷 CI | CI/CD configuration changes |
| ⬆️ Dependencies | Dependency updates |
| 🔧 Chores | Other maintenance tasks |
| 💥 Breaking Changes | Major version only (REQUIRED) |
| 🗑️ Deprecated | Minor/Major versions only |
Write for package consumers, not as git history.
Avoid vague terms:
Use specific, actionable language:
getUserList() with page and limit parameters"Major Versions:
Minor Versions:
Patch Versions:
When listing multiple items (features, agents, tools, etc.), each item should include a brief description of what it does and why it matters:
// ❌ Bad - just names without context
- Added `reviewer-changelog`
- Added `reviewer-eslint`
- Added `reviewer-prettier`
// ✅ Good - each item explains its purpose
- Added `reviewer-changelog` - Validates changelog entries have high-quality, descriptive content
- Added `reviewer-eslint` - Runs ESLint checks to catch linting violations automatically
- Added `reviewer-prettier` - Validates code formatting matches project standards
Even for simple list items, the reader should understand what the item does without needing to look elsewhere.
## ✨ Features
- Added `exportToCSV()` function for data export
- Implemented multi-select filtering in list views
## ✨ Features
### New Data Export Feature
Export data in multiple formats for analysis and reporting.
**Usage:**
\`\`\`typescript
import { exportData } from '@furystack/utils';
const result = await exportData(items, { format: 'csv' });
\`\`\`
## 💥 Breaking Changes
### API Methods Now Use Object Parameters
Methods now accept object parameters instead of positional arguments.
**Examples:**
\`\`\`typescript
// ❌ Before
await injector.getInstance(MyService, arg1, arg2);
// ✅ After
await injector.getInstance(MyService, { arg1, arg2 });
\`\`\`
**Impact:** All callers of the affected methods need to be updated.
**Migration:** Search for method calls with `grep -r "getInstance" packages/` and update to object syntax.
After filling entries, run:
yarn changelog check
This validates: