@willbooster/agent-skills 1.28.0 → 1.28.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (4) hide show
  1. package/dist/cli.js +3 -3
  2. package/package.json +1 -1
  3. package/skills/complete-pr/references/other-repositories-workflow.md +2 -2
  4. package/skills/complete-pr/references/willbooster-workflow.md +1 -1
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@willbooster/agent-skills",
3
- "version": "1.28.0",
3
+ "version": "1.28.2",
4
4
  "description": "A collection of agent skills for WillBooster Inc.",
5
5
  "repository": {
6
6
  "type": "git",
package/skills/complete-pr/references/other-repositories-workflow.md CHANGED
@@ -1,7 +1,7 @@
1
1
  1. Check the CI (GitHub Actions) results using the `check-pr-ci` skill.
2
2
  2. If any workflow fails, pull the latest remote changes, resolve the issues, commit, push, and return to step 1. Otherwise, proceed to the next step.
3
3
  3. Fetch unresolved review threads using the `manage-pr-review-threads` skill.
4
- 4. Review each unresolved thread and decide whether it requires a code or documentation change. Validate each claim against the current codebase first, and reproduce it or check official documentation when needed instead of relying on memory. Ignore only comments that are clearly outdated, incorrect, or intentionally declined with solid reasoning.
5
- 5. If there are valid review comments to address, make only the changes supported by the validation from step 4, commit, push, and then return to step 1.
4
+ 4. Review each unresolved thread and decide whether it requires a code or documentation change. Treat every review claim as unverified until you confirm it with concrete evidence from the current codebase, a local reproduction, or official documentation. Do not make changes just because a reviewer asserted them; make changes only after the evidence shows the comment is valid. Ignore only comments that are clearly outdated, incorrect, out of scope, or intentionally declined with solid reasoning.
5
+ 5. If there are valid review comments to address, make only the changes supported by the evidence from step 4, commit, push, and then return to step 1.
6
6
  - Do not post any message like review replies on non-WillBooster repositories.
7
7
  6. Update the PR title and body using the `update-pr` skill to reflect all changes.
package/skills/complete-pr/references/willbooster-workflow.md CHANGED
@@ -1,7 +1,7 @@
1
1
  1. Check the CI (GitHub Actions) results using the `check-pr-ci` skill.
2
2
  2. If any workflow fails, pull the latest remote changes, resolve the issues, commit, push, and return to step 1. Otherwise, proceed to the next step.
3
3
  3. Fetch unresolved review threads using the `manage-pr-review-threads` skill.
4
- 4. Review each unresolved thread to determine if it requires code or documentation changes. Validate each claim against the current codebase first, and reproduce issues or consult official documentation when necessary instead of relying on memory.
4
+ 4. Review each unresolved thread to determine if it requires code or documentation changes. Treat every review claim as unverified until you confirm it with concrete evidence from the current codebase, a local reproduction, or official documentation. Do not make changes just because a reviewer asserted them; make changes only after the evidence shows the comment is valid.
5
5
  5. Address valid review comments by updating the code. For invalid comments, add explanatory comments to the code detailing why the existing implementation is necessary.
6
6
  - If there are valid review comments that are out of scope for the current PR, create new issues for them.
7
7
  6. Reply to all review threads using the `manage-pr-review-threads` skill.