chore: willboosterify this repo #541
Conversation
There was a problem hiding this comment.
Pull request overview
This PR performs repository standardization ("willboosterify") by updating AI agent documentation and Yarn configuration. The changes clarify Git workflow instructions for AI agents and expand the list of pre-approved npm packages.
Key changes:
- Updated AI agent instructions to specify "non-main branch" instead of "current branch" for commits
- Added Next.js and React dependencies to Yarn's pre-approved packages list
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 4 comments.
Show a summary per file
| File | Description |
|---|---|
| GEMINI.md | Updated Git workflow instruction to clarify commits should be made to non-main branch |
| CLAUDE.md | Updated Git workflow instruction to clarify commits should be made to non-main branch |
| AGENTS.md | Updated Git workflow instruction to clarify commits should be made to non-main branch |
| .cursor/rules/general.mdc | Updated Git workflow instruction to clarify commits should be made to non-main branch |
| .yarnrc.yml | Added next, @next/*, react, and react-dom to npm pre-approved packages list |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| - After making code changes, run `yarn check-all-for-ai` to execute all tests (note: this may take up to 30 minutes), or run `yarn check-for-ai` for type checking and linting only. | ||
| - If you are confident your changes will not break any tests, you may use `check-for-ai`. | ||
| - Once you have verified your changes, commit them to the current branch using the `--no-verify` option and push to the current branch. | ||
| - Once you have verified your changes, commit them to the non-main branch using the `--no-verify` option and push to the current branch. |
There was a problem hiding this comment.
Inconsistent wording: The instruction says to "commit them to the non-main branch" but then says "push to the current branch". For clarity and consistency, consider changing this to either:
- "commit them to the non-main branch using the
--no-verifyoption and push to the non-main branch." - "commit them using the
--no-verifyoption and push to the current non-main branch."
This ensures users understand they should be working on and pushing to the same non-main branch.
| - Once you have verified your changes, commit them to the non-main branch using the `--no-verify` option and push to the current branch. | |
| - Once you have verified your changes, commit them to the non-main branch using the `--no-verify` option and push to the non-main branch. |
| - After making code changes, run `yarn check-all-for-ai` to execute all tests (note: this may take up to 30 minutes), or run `yarn check-for-ai` for type checking and linting only. | ||
| - If you are confident your changes will not break any tests, you may use `check-for-ai`. | ||
| - Once you have verified your changes, commit them to the current branch using the `--no-verify` option and push to the current branch. | ||
| - Once you have verified your changes, commit them to the non-main branch using the `--no-verify` option and push to the current branch. |
There was a problem hiding this comment.
Inconsistent wording: The instruction says to "commit them to the non-main branch" but then says "push to the current branch". For clarity and consistency, consider changing this to either:
- "commit them to the non-main branch using the
--no-verifyoption and push to the non-main branch." - "commit them using the
--no-verifyoption and push to the current non-main branch."
This ensures users understand they should be working on and pushing to the same non-main branch.
| - Once you have verified your changes, commit them to the non-main branch using the `--no-verify` option and push to the current branch. | |
| - Once you have verified your changes, commit them to the non-main branch using the `--no-verify` option and push to the non-main branch. |
| - After making code changes, run `yarn check-all-for-ai` to execute all tests (note: this may take up to 30 minutes), or run `yarn check-for-ai` for type checking and linting only. | ||
| - If you are confident your changes will not break any tests, you may use `check-for-ai`. | ||
| - Once you have verified your changes, commit them to the current branch using the `--no-verify` option and push to the current branch. | ||
| - Once you have verified your changes, commit them to the non-main branch using the `--no-verify` option and push to the current branch. |
There was a problem hiding this comment.
Inconsistent wording: The instruction says to "commit them to the non-main branch" but then says "push to the current branch". For clarity and consistency, consider changing this to either:
- "commit them to the non-main branch using the
--no-verifyoption and push to the non-main branch." - "commit them using the
--no-verifyoption and push to the current non-main branch."
This ensures users understand they should be working on and pushing to the same non-main branch.
| - Once you have verified your changes, commit them to the non-main branch using the `--no-verify` option and push to the current branch. | |
| - Once you have verified your changes, commit them to the non-main branch using the `--no-verify` option and push to the non-main branch. |
| - After making code changes, run `yarn check-all-for-ai` to execute all tests (note: this may take up to 30 minutes), or run `yarn check-for-ai` for type checking and linting only. | ||
| - If you are confident your changes will not break any tests, you may use `check-for-ai`. | ||
| - Once you have verified your changes, commit them to the current branch using the `--no-verify` option and push to the current branch. | ||
| - Once you have verified your changes, commit them to the non-main branch using the `--no-verify` option and push to the current branch. |
There was a problem hiding this comment.
Inconsistent wording: The instruction says to "commit them to the non-main branch" but then says "push to the current branch". For clarity and consistency, consider changing this to either:
- "commit them to the non-main branch using the
--no-verifyoption and push to the non-main branch." - "commit them using the
--no-verifyoption and push to the current non-main branch."
This ensures users understand they should be working on and pushing to the same non-main branch.
| - Once you have verified your changes, commit them to the non-main branch using the `--no-verify` option and push to the current branch. | |
| - Once you have verified your changes, commit them to the non-main branch using the `--no-verify` option and push to the non-main branch. |
WillBooster-bot
force-pushed
the
wbfy
branch
2 times, most recently
from
ed6fff4 to
2535ba5
Compare
No description provided.