@vfarcic/dot-ai 0.118.0 → 0.119.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vfarcic/dot-ai",
-  "version": "0.118.0",
+  "version": "0.119.0",
   "description": "AI-powered development productivity platform that enhances software development workflows through intelligent automation and AI-driven assistance",
   "mcpName": "io.github.vfarcic/dot-ai",
   "main": "dist/index.js",

package/shared-prompts/prd-done.md

@@ -53,10 +53,191 @@ Complete the PRD implementation workflow including branch management, pull reque
 - [ ] **Push to remote**: `git push -u origin feature/prd-[issue-id]-[feature-name]`
 
 ### 3. Pull Request Creation
-- [ ] **Create PR**: Use `gh pr create` with comprehensive description
-- [ ] **Link to PRD**: Reference the original issue and PRD file
-- [ ] **Review checklist**: Include testing, documentation, and quality confirmations
-- [ ] **Request reviews**: Assign appropriate team members for code review
+
+**IMPORTANT: Always check for and use PR template if available**
+
+#### 3.1. PR Template Detection and Parsing
+- [ ] **Check for PR template** in common locations:
+  - `.github/PULL_REQUEST_TEMPLATE.md`
+  - `.github/pull_request_template.md`
+  - `.github/PULL_REQUEST_TEMPLATE/` (directory with multiple templates)
+  - `docs/pull_request_template.md`
+
+- [ ] **Read and parse template comprehensively**: If found, analyze the template to extract:
+  - **Structural elements**: Required sections, checklists, format requirements
+  - **Content requirements**: What information needs to be provided in each section
+  - **Process instructions**: Any workflow enhancements or prerequisites specified in the template
+  - **Validation requirements**: Any checks, sign-offs, or verifications mentioned
+
+- [ ] **Extract actionable instructions from template**:
+  - **Commit requirements**: Look for DCO sign-off, commit message format, commit signing requirements
+  - **Pre-submission actions**: Build commands, test commands, linting, format checks
+  - **Documentation requirements**: Which docs must be updated, links that must be added
+  - **Review requirements**: Required reviewers, approval processes, special considerations
+
+  **Examples of template instructions to identify and execute:**
+  - "All commits must include a `Signed-off-by` line" → Validate commits have DCO sign-off, amend if missing
+  - "Run `npm test` before submitting" → Execute test command
+  - "PR title follows Conventional Commits format" → Validate title format
+  - "Update CHANGELOG.md" → Check if changelog was updated
+  - Any bash commands shown in code blocks → Consider if they should be executed
+
+#### 3.2. Analyze Changes for PR Content
+- [ ] **Review git diff**: Analyze `git diff main...HEAD` to understand scope of changes
+- [ ] **Review commit history**: Use `git log main..HEAD` to understand implementation progression
+- [ ] **Identify change types**: Determine if changes include:
+  - New features, bug fixes, refactoring, documentation, tests, configuration, dependencies
+  - Breaking changes or backward-compatible changes
+  - Performance improvements or security fixes
+- [ ] **Check modified files**: Identify which areas of codebase were affected
+  - Source code files
+  - Test files
+  - Documentation files
+  - Configuration files
+
+#### 3.3. Auto-Fill PR Information
+Automatically populate what can be deduced from analysis:
+
+- [ ] **PR Title**:
+  - Follow template title format if specified (e.g., Conventional Commits: `feat(scope): description`)
+  - Extract from PRD title/description and commit messages
+  - Include issue reference if required by template
+
+- [ ] **Description sections**:
+  - **What/Why**: Extract from PRD objectives and implementation details
+  - **Related issues**: Automatically link using `Closes #[issue-id]` or `Fixes #[issue-id]`
+  - **Type of change**: Check appropriate boxes based on file analysis
+
+- [ ] **Testing checklist**:
+  - Mark "Tests added/updated" if test files were modified
+  - Note: Tests run in CI/CD automatically
+
+- [ ] **Documentation checklist**:
+  - Mark items based on which docs were updated (README, API docs, code comments)
+  - Check if CONTRIBUTING.md guidelines followed
+
+- [ ] **Security checklist**:
+  - Scan commits for potential secrets or credentials
+  - Flag if authentication/authorization code changed
+  - Note any dependency updates
+
+#### 3.4. Prompt User for Information That Cannot Be Deduced
+**IMPORTANT: Don't just ask - analyze and propose answers, then let user confirm or correct**
+
+For each item, use available context to propose an answer, then present it to the user for confirmation:
+
+- [ ] **Manual testing results**:
+  - **Analyze PRD testing strategy section** to understand what testing was planned
+  - **Check git commits** for testing-related messages
+  - **Propose testing approach** based on change type (e.g., "Documentation reviewed for accuracy and clarity, cross-references validated")
+  - Present proposal and ask: "Is this accurate, or would you like to modify?"
+
+- [ ] **Breaking changes**:
+  - **Scan commits and PRD** for breaking change indicators
+  - If detected, **propose migration guidance** based on PRD content
+  - If not detected, **confirm**: "No breaking changes detected. Correct?"
+
+- [ ] **Performance implications**:
+  - **Analyze change type**: Documentation/config changes typically have no performance impact
+  - **Propose answer** based on analysis (e.g., "No performance impact - documentation only")
+  - Ask: "Correct, or are there performance considerations?"
+
+- [ ] **Security considerations**:
+  - **Check if security-sensitive files** were modified (auth, credentials, API keys)
+  - **Scan commits** for security-related keywords
+  - **Propose security status** (e.g., "No security implications - documentation changes only")
+  - Ask: "Accurate, or are there security considerations to document?"
+
+- [ ] **Reviewer focus areas**:
+  - **Analyze PRD objectives** and **git changes** to identify key areas
+  - **Propose specific focus areas** (e.g., "Verify documentation accuracy, check cross-reference links, confirm workflow examples match implementation")
+  - Present list and ask: "Are these the right focus areas, or should I adjust?"
+
+- [ ] **Follow-up work**:
+  - **Check PRD for "Future Enhancements" or "Out of Scope" sections**
+  - **Analyze other PRDs** in `prds/` directory for related work
+  - **Propose follow-up items** if any (e.g., "Future enhancements listed in PRD: template validation, AI-powered descriptions")
+  - Ask: "Should I list these, or is there other follow-up work?"
+
+- [ ] **Additional context**:
+  - **Review PRD for special considerations**
+  - **Check if this is a dogfooding/testing PR**
+  - **Propose any relevant context** (e.g., "This PR itself tests the enhanced workflow it documents")
+  - Ask: "Anything else reviewers should know?"
+
+**Presentation Format:**
+Present all proposed answers together in a summary format:
+```markdown
+📋 **Proposed PR Information** (based on analysis)
+
+**Manual Testing:** [proposed answer]
+**Breaking Changes:** [proposed answer]
+**Performance Impact:** [proposed answer]
+**Security Considerations:** [proposed answer]
+**Reviewer Focus:** [proposed list]
+**Follow-up Work:** [proposed items or "None"]
+**Additional Context:** [proposed context or "None"]
+
+Please review and respond:
+- Type "yes" or "confirm" to accept all
+- Specify corrections for any items that need changes
+```
+
+#### 3.5. Execute Template Requirements
+**IMPORTANT: Before creating the PR, identify and execute any actionable requirements from the template**
+
+- [ ] **Analyze template for actionable instructions**:
+  - Scan template content for imperative statements, requirements, or commands
+  - Look for patterns like "must", "should", "run", "execute", "ensure", "verify"
+  - Identify bash commands in code blocks that appear to be prerequisites
+  - Extract any validation requirements mentioned in checklists
+
+- [ ] **Categorize identified requirements**:
+  - **Commit-level actions**: Sign-offs, formatting, validation
+  - **Pre-submission commands**: Tests, builds, lints, format checks
+  - **Validation checks**: File existence, format compliance, content requirements
+  - **Documentation actions**: Required updates, links to add
+
+- [ ] **Propose and execute requirements**:
+  - Present identified requirements to user: "Template specifies these actions: [list]"
+  - For each requirement, determine if it can be automated
+  - Propose execution: "Should I execute these now?"
+  - Execute confirmed actions and report results
+  - Handle failures gracefully and ask user how to proceed
+
+- [ ] **Summary before PR creation**:
+  ```markdown
+  ✅ Template Requirements Status:
+  [List each requirement with status: executed/validated/skipped/failed]
+
+  Ready to create PR? (yes/no)
+  ```
+
+#### 3.6. Create Pull Request
+- [ ] **Construct PR body**: Combine auto-filled and user-provided information following template structure
+- [ ] **Create PR**: Use `gh pr create --title "[title]" --body "[constructed-body]"` or `gh pr create --title "[title]" --body-file [temp-file]`
+- [ ] **Verify PR created**: Confirm PR was created successfully and template was populated correctly
+- [ ] **Request reviews**: Assign appropriate team members for code review if specified
+
+#### 3.7. Fallback for Projects Without Templates
+If no PR template is found, create a sensible default structure:
+
+```markdown
+## Description
+[What this PR does and why]
+
+## Related Issues
+Closes #[issue-id]
+
+## Changes Made
+- [List key changes]
+
+## Testing
+- [Testing approach and results]
+
+## Documentation
+- [Documentation updates made]
+```
 
 ### 4. Review and Merge Process
 - [ ] **Check ongoing processes**: Use `gh pr checks [pr-number]` to check for any ongoing CI/CD, security analysis, or automated reviews (CodeRabbit, CodeQL, etc.)