メモ
- このライブラリの例はインスピレーションを得るためのものです。プロジェクト、言語、チーム プロセスに合わせて具体的に調整することをお勧めします。
- 特定の言語とシナリオ向けのカスタム指示のコミュニティに投稿された例については、Awesome GitHub Copilot Customizations リポジトリを参照してください。
- カスタム指示は、作成するプラットフォームまたは IDE に応じて、さまざまなスコープにわたって適用できます。 詳しくは、「GitHub Copilotの応答をカスタマイズする方法」を参照してください。
次の例は、GitHub Copilot に、適切に構造化された実用的な GitHub の issue を作成し、効果的な issue 管理を提供するように指示するカスタム手順を示しています。
When creating or managing GitHub issues: ## Bug Report Essentials **Description**: Clear, concise summary of the problem **Steps to Reproduce**: Numbered list of exact actions that cause the issue **Expected vs Actual Behavior**: What should happen vs what actually happens **Environment**: OS, browser/client, app version, relevant dependencies **Additional Context**: Screenshots, error logs, or stack traces ## Feature Request Structure **Problem**: What specific problem does this solve? **Proposed Solution**: Brief description of the suggested approach **Use Cases**: 2-3 concrete examples of when this would be valuable **Success Criteria**: How to measure if the feature works ## Issue Management Best Practices - Use clear, descriptive titles that summarize the request - Apply appropriate labels: bug/feature, priority level, component areas - Ask clarifying questions when details are missing - Link related issues using #number syntax - Provide specific next steps and realistic timelines ## Key Response Guidelines - Request reproduction steps for unclear bugs - Ask for screenshots/logs when visual issues are reported - Explain technical concepts clearly for non-technical users - Update issue status regularly with progress information Focus on making issues actionable and easy for contributors to understand.
When creating or managing GitHub issues:
## Bug Report Essentials
**Description**: Clear, concise summary of the problem
**Steps to Reproduce**: Numbered list of exact actions that cause the issue
**Expected vs Actual Behavior**: What should happen vs what actually happens
**Environment**: OS, browser/client, app version, relevant dependencies
**Additional Context**: Screenshots, error logs, or stack traces
## Feature Request Structure
**Problem**: What specific problem does this solve?
**Proposed Solution**: Brief description of the suggested approach
**Use Cases**: 2-3 concrete examples of when this would be valuable
**Success Criteria**: How to measure if the feature works
## Issue Management Best Practices
- Use clear, descriptive titles that summarize the request
- Apply appropriate labels: bug/feature, priority level, component areas
- Ask clarifying questions when details are missing
- Link related issues using #number syntax
- Provide specific next steps and realistic timelines
## Key Response Guidelines
- Request reproduction steps for unclear bugs
- Ask for screenshots/logs when visual issues are reported
- Explain technical concepts clearly for non-technical users
- Update issue status regularly with progress information
Focus on making issues actionable and easy for contributors to understand.
参考資料
- GitHub Copilotの応答をカスタマイズする方法 - GitHub Copilot での応答カスタマイズの概要
- Copilot に対してカスタム命令を追加する - カスタム指示を構成する方法
- 優れた GitHub Copilot カスタマイズ - 特定の言語とシナリオ向けにコミュニティに投稿されたカスタム指示とその他のカスタマイズのリポジトリ