Skip to content

Conversation

troystaylor
Copy link
Contributor

Pull Request Checklist

  • I have read and followed the CONTRIBUTING.md guidelines.
  • My contribution adds a new instruction, prompt, or chat mode file in the correct directory.
  • The file follows the required naming convention.
  • The content is clearly structured and follows the example format.
  • I have tested my instructions, prompt, or chat mode with GitHub Copilot.
  • I have run node update-readme.js and verified that README.md is up to date.

Description

This PR adds comprehensive Power BI development resources to the awesome-copilot collection.


Type of Contribution

  • New instruction file.
  • New prompt file.
  • New chat mode file.
  • Other (please specify): New collection file

Additional Notes


By submitting this pull request, I confirm that my contribution abides by the Code of Conduct and will be licensed under the MIT License.

@Copilot Copilot AI review requested due to automatic review settings October 7, 2025 21:01
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR adds comprehensive Power BI development resources to the awesome-copilot collection, providing extensive guidance for data modeling, DAX optimization, performance tuning, visualization design, security implementation, and DevOps practices.

Key changes include:

  • Addition of 14 new Power BI-focused files spanning prompts, instructions, and chat modes
  • Creation of a dedicated Power BI Development collection grouping all resources
  • Implementation of comprehensive Power BI guidance covering the full development lifecycle

Reviewed Changes

Copilot reviewed 18 out of 18 changed files in this pull request and generated no comments.

Show a summary per file
File Description
prompts/power-bi-report-design-consultation.prompt.md Expert consultation prompt for Power BI report visualization design with comprehensive chart selection and UX guidelines
prompts/power-bi-performance-troubleshooting.prompt.md Systematic troubleshooting guide for diagnosing and resolving Power BI performance issues
prompts/power-bi-model-design-review.prompt.md Comprehensive data model design review framework for architecture evaluation and optimization
prompts/power-bi-dax-optimization.prompt.md DAX formula optimization prompt for improving performance, readability, and maintainability
instructions/ (6 files) Best practices instructions covering security/RLS, report design, DevOps/ALM, DAX, data modeling, and custom visuals development
collections/power-bi-development.md New collection file organizing all Power BI resources with installation links and descriptions
chatmodes/ (4 files) Expert chat modes for visualization, performance, DAX, and data modeling guidance
README updates Integration of new Power BI resources into main documentation with proper categorization

Copy link
Contributor

@aaronpowell aaronpowell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Many of the chat modes, instructions, and prompts have fenced code blocks around the entire file. This will cause problems with GitHub Copilot, so can you correct them to be correctly formatted markdown.

…nced code blocks

- Add power-bi-development.collection.yml with proper metadata
- Remove outer 4-backtick fences from all Power BI files (chatmodes, instructions, prompts)
- Files now have only the standard 3-backtick fences for proper GitHub Copilot compatibility
Copy link
Contributor

@aaronpowell aaronpowell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's still a number of additions that have code fences around the whole file

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants