feat(config): add Cursor automation rules for enhanced development workflow

[RodolfoBonis]

Pull Request: feat(config): add Cursor automation rules for enhanced development workflow

📋 Summary

This Pull Request introduces automation rules for the Cursor framework aimed at standardizing and optimizing the development workflow. The changes include automation for commits, detailed PR analysis, and automated PR creation.

🔧 Type of Change

• ✨ Feature (new functionality)
• 🐛 Bug fix (bug fix)
• 🔥 Breaking change (change that breaks compatibility)
• 📝 Documentation (documentation update)
• 🎨 Style (formatting, no functional change)
• ♻️ Refactor (code refactoring)
• ⚡ Performance (performance improvement)
• ✅ Test (test addition or correction)
• 🔧 Chore (maintenance, configuration)

📁 Modified Files

• .cursor/rules/commit-flow.mdc - Automation rules for commits using conventional commits.
• .cursor/rules/pr-analysis.mdc - Robust rules for detailed Pull Request analysis.
• .cursor/rules/pr-creation.mdc - Rules for automated PR creation with comprehensive descriptions.

💡 Motivation and Context

The primary goals of this implementation are to:

• Standardize the commit process through the use of conventional commits.
• Automate detailed PR analysis with multiple fallback strategies to ensure reliability.
• Enable automatic creation of PRs with structured and informative descriptions.
• Enhance the quality and consistency of the development workflow.
• Reduce the time spent on repetitive versioning tasks.

🚀 Added Features

🔄 Commit Flow Automation

• Automatic analysis of changes.
• Individual commits per file.
• Automatic classification of change types.
• Standardized messages following conventional commits.

🔍 PR Analysis Automation

• Robust data collection via GitHub API.
• Multiple fallback strategies (cURL → gh CLI → tools).
• Detailed analysis with insights and recommendations.
• Comprehensive reports provided in Portuguese.

✨ PR Creation Automation

• Automatic generation of structured descriptions.
• Analysis of changes and classification.
• Automatic detection of the target branch.
• Standardized templates for different PR types.

📝 Included Commits

• 59f44b3: feat(config): add Cursor automation rules for commit flow, PR analysis, and creation

✅ Checklist

• Rules implemented and tested.
• Comprehensive documentation of functionalities.
• Support for multiple fallback strategies.
• Standardization of conventional commits.
• Complete automation of the development workflow.

🎯 Expected Benefits

• Consistency: Standardization of commits and PRs.
• Efficiency: Reduction in time spent on repetitive tasks.
• Quality: Detailed and structured analyses.
• Robustness: Multiple fallback strategies to ensure functionality.
• Productivity: Automation of manual processes.

🔧 How to Use

After merging, the rules will be automatically applied when:

• Requesting "commit the changes" or "commit as mudanças".
• Requesting "analyze PR #123" or "analise o PR #123".
• Requesting "create PR" or "criar PR para main".

⚠️ Considerations for Reviewers

• Ensure that the automation rules align with existing workflows and do not conflict with any current practices.
• Review the fallback strategies for data collection to confirm reliability and efficiency.
• Assess the clarity and usefulness of the generated PR descriptions.

---

Conclusion: This implementation establishes a solid foundation for automating the development workflow, providing increased efficiency and consistency in versioning and collaboration processes. Your feedback and suggestions for improvement are highly appreciated!

[github-actions]

Code Review by OpenAI

Prompt too long for OpenAI: 19005 characters, sending only first 8000 characters
This commit introduces two new files: commit-flow.mdc and pr-analysis.mdc, which outline automation rules for committing changes and analyzing pull requests respectively. Here’s a detailed review of the changes:

General Feedback

1. Clarity and Structure: The documents are well-structured, with clear sections that guide the user through the process. The use of headings and lists makes it easy to follow.

2. Consistency: The formatting is consistent throughout the documents. The use of code blocks for commands and guidelines is effective, making it easy to distinguish between explanations and executable commands.

3. Thoroughness: Both documents cover a comprehensive range of scenarios and provide detailed instructions, which is beneficial for users who may not be familiar with the processes.

Specific Feedback on commit-flow.mdc

1. Objective Clarity: The objective is clearly stated, and the rationale for automating the commit process is well-defined.

2. Commit Message Structure: The section detailing the commit message structure is clear. However, it might be beneficial to include an example of a breaking change in the footer.

3. Classification Rules: The classification rules are useful, but consider adding examples for each commit type to provide further clarity.

4. Conciseness: The guideline to keep descriptions concise (max 50 characters) is excellent. It might be helpful to mention that this is a convention in many projects.

5. Final Summary: The inclusion of a final summary of created commits is a great touch, as it helps users keep track of what has been committed.

Specific Feedback on pr-analysis.mdc

1. Data Collection Strategy: The stratified approach to data collection (primary, secondary, tertiary) is logical and provides a fallback mechanism that enhances robustness.

2. Parallel Execution: The emphasis on parallel execution for data collection is excellent for performance. However, ensure that users understand the importance of handling potential race conditions or dependencies between the commands.

3. Data Processing: The section on data processing could benefit from a brief explanation of how to handle the JSON responses, especially for users who may not be familiar with JSON parsing.

4. Enhanced Analysis Report Structure: The report structure is well-thought-out. However, it might be helpful to include a brief note on how to format the dates mentioned in the report.

5. Language Consideration: The report structure includes sections in Portuguese (e.g., "Análise Detalhada do", "Objetivo e Motivação"). Ensure that this aligns with the user base's language preferences or consider providing translations.

Suggestions for Improvement

• Examples: Consider adding more examples throughout both documents to illustrate the concepts being discussed, especially in the classification and analysis sections.
• Error Handling: Include guidance on how to handle errors or unexpected responses during the execution of the commands, especially in the PR analysis section.
• Testing: If possible, include a note about testing the automation rules in a safe environment before deploying them in a production scenario.

Conclusion

Overall, the commit adds valuable automation rules that can significantly enhance the workflow for committing changes and analyzing pull requests. The documents are clear, comprehensive, and structured well, making them easy to follow. With a few enhancements and clarifications, they will serve as an excellent resource for users.