Install dependencies by running:

npm install

Ensure all unit tests pass by running:

npm run test

Unit tests should exist in the `__tests__` directory. They are powered by

`jest`. Fixtures should be placed in the `__fixtures__` directory.

- Follow standard TypeScript and JavaScript coding conventions and best

practices

- Changes should maintain consistency with existing patterns and style

- Document changes clearly and thoroughly, including updates to existing

comments when appropriate

- Do not include basic, unnecessary comments that simply restate what the code

is doing (focus on explaining _why_, not _what_)

- Use consistent error handling patterns throughout the codebase

- Use TypeScript's type system to ensure type safety and clarity

- Keep functions focused and manageable

- Use descriptive variable and function names that clearly convey their purpose

- Use JSDoc comments to document functions, classes, and complex logic

- After doing any refactoring, ensure to run `npm run test` to ensure that all

tests still pass and coverage requirements are met

- When suggesting code changes, always opt for the most maintainable approach.

Try your best to keep the code clean and follow "Don't Repeat Yourself" (DRY)

principles

- Avoid unnecessary complexity and always consider the long-term maintainability

of the code

- When writing unit tests, try to consider edge cases as well as the main path

of success. This will help ensure that the code is robust and can handle

unexpected inputs or situations

GitHub Actions are versioned using branch and tag names. Please ensure the

version in the project's `package.json` is updated to reflect the changes made

in the codebase. The version should follow

[Semantic Versioning](https://semver.org/) principles.

When creating a pull request (PR), please ensure that:

- Keep changes focused and minimal (avoid large changes, or consider breaking

them into separate, smaller PRs)

- Formatting checks pass

- Linting checks pass

- Unit tests pass and coverage requirements are met

- If necessary, the `README.md` file is updated to reflect any changes in

functionality or usage

The body of the PR should include:

- A summary of the changes

- A special note of any changes to dependencies

- A link to any relevant issues or discussions

- Any additional context that may be helpful for reviewers

When performing a code review, please follow these guidelines:

- If there are changes that modify the functionality/usage of the action,

validate that there are changes in the `README.md` file that document the new

or modified functionality

{

"servers": {

"github": {

"url": "https://api.githubcopilot.com/mcp/",

"type": "http"

}

},

"inputs": []

}

{

"github.copilot.chat.reviewSelection.instructions": [

{

"text": "Review the code changes carefully before accepting them."

}

],

"github.copilot.chat.commitMessageGeneration.instructions": [

{

"text": "Use conventional commit message format."

}

],

"github.copilot.chat.pullRequestDescriptionGeneration.instructions": [

{ "text": "Always include a list of key changes." }

]

}