chore: lint + format

Author: bhouston

.github/workflows/mycoder-issue-triage.yml

@@ -35,4 +35,5 @@ jobs:
       - run: |
           echo "${{ secrets.GH_PAT }}" | gh auth login --with-token
           gh auth status
-      - run: mycoder --upgradeCheck false --githubMode true --userPrompt false "You are an issue triage assistant. Please analyze GitHub issue ${{ github.event.issue.number }} according to the guidelines in .mycoder/ISSUE_TRIAGE.md. Categorize the issue type (Bug, Feature, Request), suggest appropriate labels, check for duplicates, and provide a helpful initial assessment. If the issue is too vague, ask for more information. For bugs, try to identify potential causes. For feature requests, suggest implementation approaches. For questions, try to provide answers based on the codebase and documentation."
+      - run: |
+          mycoder --upgradeCheck false --githubMode true --userPrompt false "You are an issue triage assistant. Please analyze GitHub issue ${{ github.event.issue.number }} according to the guidelines in .mycoder/ISSUE_TRIAGE.md"

.github/workflows/mycoder-pr-review.yml

@@ -45,4 +45,5 @@ jobs:
           PR_COMMENTS=$(gh pr view ${{ github.event.pull_request.number }} --json comments --jq '.comments')
           echo "reviews=$PR_REVIEWS" >> $GITHUB_OUTPUT
           echo "comments=$PR_COMMENTS" >> $GITHUB_OUTPUT
-      - run: mycoder --upgradeCheck false --githubMode true --userPrompt false "Please review PR ${{ github.event.pull_request.number }} according to the guidelines in .mycoder/PR_REVIEW.md. This PR is related to issue ${{ github.event.pull_request.head.ref }} and has the title '${{ github.event.pull_request.title }}'. Review the PR changes, check if it addresses the requirements in the linked issue, and provide constructive feedback. Consider previous review comments and discussions to avoid repetition and help move towards resolution. Previous reviews and comments: ${{ steps.get-reviews.outputs.reviews }} ${{ steps.get-reviews.outputs.comments }}"
+      - run: |
+          mycoder --upgradeCheck false --githubMode true --userPrompt false "Please review PR ${{ github.event.pull_request.number }} according to the guidelines in .mycoder/PR_REVIEW.md. Previous reviews and comments: ${{ steps.get-reviews.outputs.reviews }} ${{ steps.get-reviews.outputs.comments }}"

.mycoder/ISSUE_TRIAGE.md

@@ -5,11 +5,13 @@
 When triaging a new issue, categorize it by type and apply appropriate labels:
 
 ### Issue Types
+
 - **Bug**: An error, flaw, or unexpected behavior in the code
 - **Feature**: A request for new functionality or capability
 - **Request**: A general request that doesn't fit into bug or feature categories
 
 ### Issue Labels
+
 - **bug**: For issues reporting bugs or unexpected behavior
 - **documentation**: For issues related to documentation improvements
 - **question**: For issues asking questions about usage or implementation
@@ -20,16 +22,19 @@ When triaging a new issue, categorize it by type and apply appropriate labels:
 ## Triage Process
 
 ### Step 1: Initial Assessment
+
 1. Read the issue description thoroughly
 2. Determine if the issue provides sufficient information
    - If too vague, ask for more details (reproduction steps, expected vs. actual behavior)
    - Check for screenshots, error messages, or logs if applicable
 
 ### Step 2: Categorization
+
 1. Assign the appropriate issue type (Bug, Feature, Request)
 2. Apply relevant labels based on the issue content
 
 ### Step 3: Duplication Check
+
 1. Search for similar existing issues
 2. If a duplicate is found:
    - Apply the "duplicate" label
@@ -39,6 +44,7 @@ When triaging a new issue, categorize it by type and apply appropriate labels:
 ### Step 4: Issue Investigation
 
 #### For Bug Reports:
+
 1. Attempt to reproduce the issue if possible
 2. Investigate the codebase to identify potential causes
 3. Provide initial feedback on:
@@ -48,6 +54,7 @@ When triaging a new issue, categorize it by type and apply appropriate labels:
    - Estimation of complexity
 
 #### For Feature Requests:
+
 1. Evaluate if the request aligns with the project's goals
 2. Investigate feasibility and implementation approaches
 3. Provide feedback on:
@@ -57,11 +64,13 @@ When triaging a new issue, categorize it by type and apply appropriate labels:
    - Estimation of work required
 
 #### For Questions:
+
 1. Research the code and documentation to find answers
 2. Provide clear and helpful responses
 3. Suggest documentation improvements if the question reveals gaps
 
 ### Step 5: Follow-up
+
 1. Provide a constructive and helpful comment
 2. Ask clarifying questions if needed
 3. Suggest next steps or potential contributors
@@ -81,4 +90,4 @@ When triaging a new issue, categorize it by type and apply appropriate labels:
 - For security vulnerabilities, suggest proper disclosure channels
 - For major feature requests, suggest discussion in appropriate forums first
 - For issues affecting performance, request benchmark data if not provided
-- For platform-specific issues, request environment details
+- For platform-specific issues, request environment details

.mycoder/PR_REVIEW.md

@@ -70,4 +70,4 @@ When reviewing updates to a PR:
 - Avoid repeating previous feedback unless clarification is needed
 - Help move the PR towards completion rather than finding new issues
 
-Remember that the goal is to help improve the code while maintaining a positive and constructive environment for all contributors.
+Remember that the goal is to help improve the code while maintaining a positive and constructive environment for all contributors.