al-pr-prepare
Prepare a clean, documented pull request draft for AL features or fixes with summary, testing notes, and checklist. ALDC workflow (Copilot prompt al-pr-prepare); invoke explicitly.
javiarmesto · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add javiarmesto/ALDC-AL-Development-Collection --skill al-pr-prepare技能说明
name: al-pr-prepare description: "Prepare a clean, documented pull request draft for AL features or fixes with summary, testing notes, and checklist. ALDC workflow (Copilot prompt al-pr-prepare); invoke explicitly." disable-model-invocation: true
Claude Code runtime: read
${CLAUDE_PROJECT_DIR}/claude-plugin/docs/claude-runtime.mdbefore running this workflow (gates, tools, paths,<Name from $ARGUMENTS>inputs). It runs in the main session.
AL Pull Request Preparation
Your goal is to prepare a pull request draft for the branch <Branch from $ARGUMENTS> summarizing all modifications, test evidence, and validation steps.
🔒 Human Gate: Pre-PR Review
Before generating PR draft document:
- Review code changes - Present summary of all modifications
- Security check - Confirm no sensitive data in commits
- Quality validation - Verify tests pass and build succeeds
- Human approval required - Obtain confirmation before creating PR draft
Process
1. Change Analysis
Inspect Branch Differences
Use git through Bash (read-only) to analyze modifications and gather context:
git diff --stat main...<Branch from $ARGUMENTS>
git log --oneline main..<Branch from $ARGUMENTS>
Gather:
- Modified files and line counts
- New files added
- Deleted files
- Commit messages and references
- Related issues or work items
Classify Changes
Categorize into:
- New Features - New AL objects, functionality, APIs
- Bug Fixes - Corrections, refactors, optimizations
- Tests - Test codeunits, scenarios, data
- Configuration - app.json, permissions, dependencies
- Documentation - README, comments, API docs
2. Extract Metadata
Find References: Scan commit messages for:
- Issue references (#123)
- Work item IDs
- Requirement numbers
Pattern matching:
- Fixes #123
- Closes #456
- Related to WORK-789
Identify Reviewers:
If <Reviewer from $ARGUMENTS> is specified, include in the draft.
3. Generate PR Draft
Create /reports/pr-draft.md with this structure:
# Pull Request: [Feature/Fix Title]
**Branch:** `<Branch from $ARGUMENTS>`
**Target:** `main`
**Author:** [Author Name]
**Date:** [Current Date]
## Overview
[2-3 sentence description of changes]
**Type of Change:**
- [ ] New Feature
- [ ] Bug Fix
- [ ] Refactoring
- [ ] Performance Improvement
- [ ] Documentation
- [ ] Configuration Change
## Related Issues
- Closes #[issue-number]
- Relates to #[issue-number]
## Changes Summary
### File Changes
| Category | Files | +Lines | -Lines |
|----------|-------|--------|--------|
| New Features | [#] | [#] | [#] |
| Bug Fixes | [#] | [#] | [#] |
| Tests | [#] | [#] | [#] |
| Docs | [#] | [#] | [#] |
| **Total** | **[#]** | **[#]** | **[#]** |
### AL Objects Modified
#### New Objects
| Type | ID | Name | Purpose |
|------|----|----- |---------|
| Table | [ID] | [Name] | [Purpose] |
| Page | [ID] | [Name] | [Purpose] |
| Codeunit | [ID] | [Name] | [Purpose] |
#### Modified Objects
| Type | ID | Name | Changes |
|------|----|----- |---------|
| TableExt | [ID] | [Name] | [Description] |
| PageExt | [ID] | [Name] | [Description] |
#### Deleted Objects
| Type | ID | Name | Reason |
|------|----|----- |-------|
| [Type] | [ID] | [Name] | [Reason] |
## Technical Details
### Architecture Changes
[Describe design pattern or architecture changes]
### Dependencies
**New:** [List new dependencies]
**Modified:** [old version → new version]
**Removed:** [List removed dependencies]
### Database Changes
- [ ] New tables
- [ ] New fields
- [ ] Modified fields
- [ ] New keys
**Migration Notes:** [Any data migration needed]
### API Changes
**New Endpoints:**
- `GET /api/[endpoint]` - [Description]
**Modified Endpoints:**
- `[Method] /api/[endpoint]` - [Changes]
**Breaking Changes:** [List breaking changes]
### Events
**Published:** [New events and purpose]
**Subscribed:** [New subscribers and purpose]
## Testing
### Test Scenarios
1. **Scenario:** [Description]
- **Steps:** [How to test]
- **Expected:** [Expected result]
- **Result:** ✅ Pass / ❌ Fail
### Automated Tests
- ✅ Unit Tests: [X/Y passed]
- ✅ Integration Tests: [X/Y passed]
- ✅ Code Coverage: [X]%
### Performance Impact
- [ ] No impact
- [ ] Improvement: [Details]
- [ ] Potential impact: [Mitigation]
## Review Checklist
### Code Quality
- [ ] Follows AL naming conventions
- [ ] Follows AL style guidelines
- [ ] No compiler warnings
- [ ] Error handling implemented
- [ ] Logging adequate
### Security
- [ ] No hardcoded secrets
- [ ] Permissions reviewed
- [ ] Input validation
- [ ] No SQL injection risks
### Testing
- [ ] All tests pass
- [ ] New code has tests
- [ ] Edge cases tested
- [ ] Manual testing done
### Documentation
- [ ] Code comments added
- [ ] API docs updated
- [ ] README updated
- [ ] Help text added
### BC Specific
- [ ] Object IDs in range
- [ ] Event patterns correct
- [ ] Page layouts user-friendly
- [ ] Translations handled
### Deployment
- [ ] Build succeeds
- [ ] Package creates
- [ ] Deployment steps documented
- [ ] Rollback plan ready
## Deployment Notes
### Steps
1. [Deployment instructions]
2. [Configuration changes]
3. [Verification steps]
### Prerequisites
[Requirements for deployment]
### Rollback Plan
[How to rollback if needed]
## Screenshots
### Before
[Previous state]
### After
[New state]
## Additional Notes
### Known Issues
[Limitations or known issues]
### Future Enhancements
[Potential improvements]
### Breaking Changes
[Breaking changes affecting existing functionality]
## Reviewer Notes
**Suggested Reviewers:**
- <Reviewer from $ARGUMENTS> - [Reason]
**Focus Areas:**
1. [Area to review carefully]
2. [Another focus area]
**Questions:**
[Specific questions or concerns]
---
**Generated by:** AL PR Preparation Workflow
**Generated on:** [Timestamp]
Output
Primary: /reports/pr-draft.md
Format: Complete markdown document