github-copilot-prompts

KO | EN

gitlite — search

#javascript #php #dotfiles #c-plus-plus #java #python #abandoned #opencv #ruby #linux #chezmoi #cpp

github-copilot-prompts

★ 43 Open GitHub ↗

No description available.

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

## GitHub Copilot Prompts

This repo contains my collection of GitHub Copilot prompts for my personal learning and reference. I'm making this repo public in the hope that it may be useful to others.

> [!IMPORTANT]
> **_Many of the prompts here are not my own. I've added prompts I found useful as read through sources such as [GitHub](https://github.blog/ai-and-ml/github-copilot/), [VS Code](https://code.visualstudio.com/docs/copilot/copilot-customization) and [Open AI](https://cookbook.openai.com/examples/gpt4-1_prompting_guide). I've also added prompts that I've learned from people that I interact with. If you recognize your prompt here and would like me to credit you, please let me know. I will be happy to do so._**

> [!WARNING]
> I use this repo frequently for my demos as I share my learnings with others. You might see small changes from time to time (sometimes due to me accidentally pushing in-the-moment demos). Apologies in advance!

## Persona Prompts
The prompts I experimented with are grouped by _persona_. These are all in the `/personas` folder.
- `/app-dev` - contains prompts useful for application developers,
- `/test-engineer` - contains prompts useful for test engineers,
- `/data-engineer` - contains prompts useful for data engineers,
- `/infra-engineer` - contains prompts useful for infrastructure engineers,
- `/ai-engineer` - contains prompts useful for AI/ML engineers,
- and so on...

So that I can freely add prompts with minimal effort to update this readme, I will also make the file names as descriptive as possible.
Each file will have a prefix:
- `editor-` - indicates that the prompt is typed directly in the code editor (also known as GitHub Copilot code completion). In most cases, these files will have the file extension of the programming language that the prompt is for (e.g. `.js` for Javascript, `.py` for Python, etc.).
- `chat-` - indicates that the prompt is used in GitHub Copilot Chat or CMD/CTRL+I. Since these prompts are for chat, the file extensions are in `.txt`.
- `edits-` - indicates that the prompt is used in Copilot Edits.
- `agent-` - indicates that the prompt is used for Copilot Agent Mode.
- files that do not have the above prefixes are extra files used by other prompts.

> [!NOTE]
> The prompts in this repo are mostly tested using VSCode with an GitHub Copilot Individual/Business license. I will indicate if there is a prompt that requires GitHub Enterprise.

## /.github Folder
My `/.github` folder is organized according to my point of view on how it should be organized and potentially shared to large dev teams. I posted the TL;DR of my thoughts in this [blog](https://raffertyuy.com/raztype/ghcp-custom-prompts-structure/), but note that this repo is more updated than the blog.

## GitHub Actions
This repo contains an experimental github action that will push the custom prompts in `/.github/**/*.md` to a list of target repos.

```mermaid
graph LR
    A[Source Repo] -->|Get .md files| B[.github/*.md]
    B --> C{Sync to Target Repos}
    C -->|Copy| D[Target Repo 1]
    C -->|Copy| E[Target Repo 2]
    C -->|Copy| F[Target Repo n]
```

> [!NOTE]
> At this time, I am assuming that direct push to the main branch is possible. If branching is required for the target repo, this experimental workflow needs to be revised.

This requires to set a GitHub Actions secret called `TARGET_REPOSITORIES`, with a JSON array of the target repositories.  For example:

```json
[
  {
    "url": "github.com/octodemo/bookstore-raffertyuy",
    "pat": "PAT_HERE"
  },
  {
    "url": "dev.azure.com/raztype/Bookstore/_git/Bookstore",
    "pat": "PAT_HERE"
  }
]
```

github-copilot-prompts

Explore Similar Repositories

Was this content helpful?

Recent Feedback

Download README