Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ed012ce31b
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| .DS_Store | ||
| node_modules/ | ||
| coverage/ | ||
| *.log | ||
| .idea/ |
There was a problem hiding this comment.
Restore ignore rules for generated artifacts
Deleting this file removes ignores for node_modules/, coverage output, IDE metadata, and logs, so routine local commands like npm install/npm test will leave large untracked trees in the worktree and make accidental commits much more likely. Keeping these ignore entries is important for maintainability and clean reviews.
Useful? React with 👍 / 👎.
| MIT License | ||
|
|
||
| Copyright (c) 2026 Mo | ||
|
|
||
| Permission is hereby granted, free of charge, to any person obtaining a copy |
There was a problem hiding this comment.
Reintroduce the repository license file
Removing LICENSE drops the explicit grant that allowed reuse and distribution of this template, which can block downstream adoption and packaging even when the code itself works. Unless intentionally relicensing in the same change, this should be restored to avoid a release/legal regression.
Useful? React with 👍 / 👎.
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 1671bbe1ff
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| const mainBranch = "main"; | ||
| const initializedGit = await ensureGitRepository(repoRoot, mainBranch); | ||
| const initializedGit = dryRun ? false : await ensureGitRepository(repoRoot, mainBranch); |
There was a problem hiding this comment.
Fail upgrade when target is not an existing git repo
--upgrade is described as refreshing an already bootstrapped repository, but this path still executes git initialization on any non-dry-run target. If the user passes a mistyped path or a non-repo directory, the command succeeds by creating a new repository and writing template files instead of failing, which can make the real upgrade silently not happen on the intended repo.
Useful? React with 👍 / 👎.
| await writeAgentsFile(repoRoot); | ||
| await copyDocs(repoRoot); | ||
| await copySkills(repoRoot); | ||
| await writeTemplateReadme(repoRoot, { dryRun, actions }); |
There was a problem hiding this comment.
Do not create README.md during upgrade
Upgrade policy says README.md is skipped, but upgrade currently always calls writeTemplateReadme, which uses overwrite: false and therefore creates README.md whenever it is missing. In repositories that intentionally removed or renamed README.md, running --upgrade will unexpectedly reintroduce template README content and produce unintended diffs.
Useful? React with 👍 / 👎.
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
No description provided.