Prompt templates for continuous integration updates

Here are some prompt templates that you can use for continuous integration (CI) updates:

1. General CI Build Update

Prompt:
“Provide a concise update on the latest build status, including any issues encountered, testing results, and any required changes for the next build.”

Example Output:

• Build Status: Success / Failure

• Issues: (List of encountered issues or blockers)

• Test Results: (Results from unit tests, integration tests, etc.)

• Required Changes: (Any tasks or changes needed for the next iteration)

---

2. Failed Build Notification

Prompt:
“Provide a detailed report on the failed build, including the error logs, the affected module/component, and potential causes of the failure.”

Example Output:

• Build Status: Failure

• Error Logs: (Details from the CI/CD system, including error message and stack trace)

• Affected Module: (Which module or feature is impacted)

• Potential Causes: (Possible reasons for the failure based on the error logs)

• Suggested Fixes: (Any immediate suggestions for fixing the issue)

---

3. Successful Build Update

Prompt:
“Provide a summary of a successful build, including which features were tested, new changes, and any improvements made to the CI pipeline.”

Example Output:

• Build Status: Success

• New Features: (List any new features or updates in the build)

• Test Results: (Successful tests or passed test cases)

• CI Pipeline Improvements: (Updates or optimizations made to the CI pipeline)

• Next Steps: (Next features or tests to focus on)

---

4. Test Coverage Report

Prompt:
“Provide a summary of test coverage results, highlighting any areas of low coverage and potential actions to improve it.”

Example Output:

• Total Test Coverage: (Percentage of code covered by tests)

• Low Coverage Areas: (Modules, features, or files with low test coverage)

• Actions to Improve Coverage: (Suggestions on how to improve coverage, such as adding unit tests for specific functions)

---

5. Merge Conflict Report

Prompt:
“Provide a report on any merge conflicts that occurred during the CI pipeline, including the conflicting files and suggested resolutions.”

Example Output:

• Merge Conflicts: (List of files with conflicts)

• Conflicting Branches: (Branches that were involved in the conflict)

• Suggested Resolutions: (Recommended steps for resolving the conflicts, such as manual merge or rebasing)

---

6. Deployment Status Update

Prompt:
“Provide an update on the latest deployment, including any deployment failures, successes, or environmental issues.”

Example Output:

• Deployment Status: Success / Failure

• Deployment Logs: (Key logs or messages from the deployment process)

• Issues Encountered: (Any failures or environmental problems during deployment)

• Next Steps: (Any actions to ensure a smoother deployment process next time)

---

7. CI Pipeline Performance Report

Prompt:
“Generate a report on the performance of the CI pipeline, focusing on build times, any slow stages, and any optimizations implemented.”

Example Output:

• Average Build Time: (Time taken for builds)

• Slowest Stages: (Stages in the pipeline that take the most time)

• Pipeline Optimizations: (Improvements or optimizations that have been applied to speed up the pipeline)

---

8. Code Linting and Quality Check Results

Prompt:
“Provide a summary of the code linting and quality checks, highlighting any warnings, errors, and areas for improvement.”

Example Output:

• Linting Status: (Passed / Failed)

• Warnings: (Any linting warnings or issues found)

• Errors: (Any errors detected during the quality check)

• Improvement Areas: (Suggestions for improving code quality based on the results)

---

9. Security Vulnerability Scan Report

Prompt:
“Provide a summary of the latest security vulnerability scan, including any critical issues identified and the recommended fixes.”

Example Output:

• Vulnerability Scan Status: (Passed / Failed)

• Critical Issues: (List of high-priority vulnerabilities found)

• Recommended Fixes: (Actionable steps to address the vulnerabilities)

• Next Steps: (Follow-up tasks or areas that need closer attention)

---

10. Environment Configuration Update

Prompt:
“Provide an update on the changes to the environment configurations, including new environment variables, updated dependencies, or configuration files.”

Example Output:

• Updated Environment Variables: (New or modified environment variables)

• Dependency Updates: (New dependencies added or old ones updated)

• Configuration Files: (Changes made to config files)

• Impact: (How these updates may affect builds or deployments)

---

These templates should help streamline the process of updating and reporting on continuous integration tasks!