Skip to content

Commit dd3adef

Browse files
WillBooster-botWillBooster-bot
committed
chore: willboosterify this repo
1 parent 0cd705b commit dd3adef

File tree

57 files changed

+875
-251
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

57 files changed

+875
-251
lines changed

‎.agents/skills/check-pr-ci/SKILL.md‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
---
2+
name: check-pr-ci
3+
description: Check the latest test-related CI results for the current pull request.
4+
allowed-tools: Bash(bun:*), Bash(gh:*), Bash(git:*)
5+
---
6+
7+
# Check PR CI
8+
9+
Run the following command from the repository root with 1 hour timeout to inspect the latest CI status: `bunx @willbooster/agent-skills@latest check-pr-ci`
10+
It classifies the latest result of each workflow as `successful`, `running`, or `failed`.

‎.agents/skills/complete-pr/SKILL.md‎

Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,30 @@
1+
---
2+
name: complete-pr
3+
description: Complete GitHub pull requests by iterating on CI and review feedback until the PR is ready.
4+
---
5+
6+
Use this skill when the goal is to drive a PR to a merge-ready state rather than just inspect it once.
7+
First, fetch the current repository owner with `gh repo view --json owner --jq '.owner.login'`.
8+
If the owner is `WillBooster` or `WillBoosterLab`, follow the first workflow below.
9+
Otherwise, follow the second workflow below.
10+
11+
## Workflow for `WillBooster` or `WillBoosterLab` repositories
12+
13+
1. Read the PR body and its messages with the `fetch-pr` skill.
14+
2. Check the results of CI (GitHub Actions) with the `check-pr-ci` skill.
15+
3. If any workflow has failed, fix the CI issues, commit, push, and then return to step 2. Otherwise, go to step 4.
16+
4. Fetch unresolved review threads with the `manage-pr-review-threads` skill.
17+
5. 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.
18+
6. If there are valid review comments to address, make only the changes supported by the validation from step 5, commit, push, and post `/gemini review` to the PR.
19+
7. Reply to all review threads with the `manage-pr-review-threads` skill.
20+
8. If you made any changes in step 6, wait for 5 minutes (`sleep 5m`) then return to step 2. Otherwise, stop.
21+
22+
## Workflow for the other repositories
23+
24+
1. Read the PR body and its messages with the `fetch-pr` skill.
25+
2. Check the results of CI (GitHub Actions) with the `check-pr-ci` skill.
26+
3. If any workflow has failed, fix the CI issues, commit, push, and then return to step 2. Otherwise, go to step 4.
27+
4. Fetch unresolved review threads.
28+
5. 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.
29+
6. If there are valid review comments to address, make only the changes supported by the validation from step 5, commit, push, and then return to step 2. Otherwise, stop.
30+
- Do not post any message like review replies on non-WillBooster repositories.

‎.agents/skills/fetch-issue/SKILL.md‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
---
2+
name: fetch-issue
3+
description: Fetch a GitHub issue body and its messages for the current repository or an issue URL.
4+
allowed-tools: Bash(bun:*), Bash(gh:*)
5+
---
6+
7+
# Fetch GitHub Issue Messages
8+
9+
Run the following command to fetch the issue body and its messages: `bunx @willbooster/agent-skills@latest fetch-issue <issue-number-or-url>`

‎.agents/skills/fetch-pr/SKILL.md‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
---
2+
name: fetch-pr
3+
description: Fetch a GitHub pull request body and its messages for the current repository or a pull request URL.
4+
allowed-tools: Bash(bun:*), Bash(gh:*)
5+
---
6+
7+
# Fetch GitHub PR Messages
8+
9+
Run the following command to fetch the pull request body and messages, excluding inline review comments: `bunx @willbooster/agent-skills@latest fetch-pr <pr-number-or-url>`

‎.agents/skills/fix-bug/SKILL.md‎

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
---
2+
name: fix-bug
3+
description: Fix a reported bug by first enhancing tests until the bug is reproduced, then fixing the implementation, and finally confirming the enhanced tests pass.
4+
---
5+
6+
Use this skill when you are asked to fix a specific bug in an existing codebase.
7+
Do not start by changing production code. First, make the bug concrete with a failing test or an equivalent automated reproduction.
8+
9+
# Bug fix workflow
10+
11+
1. Understand the reported bug precisely.
12+
- Identify the expected behavior, the actual behavior, and the smallest scope that reproduces the problem.
13+
2. Inspect the existing tests and locate the best place to extend them.
14+
- Prefer enhancing an existing focused test file over adding a broad new one.
15+
3. Before modifying tests, gather debugging evidence that helps explain the failure mode.
16+
- Use logging, screenshots, traces, or other lightweight diagnostics that fit the stack.
17+
4. Enhance the tests until they reproduce the bug.
18+
- If a relevant test already fails for the bug, keep it as the reproduction and tighten it only if needed.
19+
- Stop once the reproduction is minimal, reliable, and clearly tied to the reported bug.
20+
5. Fix the implementation without weakening the new or existing assertions.
21+
- Keep the code change as small and cohesive as possible.
22+
6. Run the enhanced tests and confirm they pass with the fix in place.
23+
7. If the repository workflow requires broader verification, run the relevant checks after the targeted tests pass.
24+
8. Summarize the root cause, the test enhancement, and the implementation fix.

‎.agents/skills/manage-pr-review-threads/SKILL.md‎

Lines changed: 35 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
---
2+
name: manage-pr-review-threads
3+
description: Inspect unresolved review threads for the current pull request, then reply to and resolve them as needed.
4+
allowed-tools: Bash(bun:*), Bash(gh:*), Bash(git:*)
5+
---
6+
7+
# Manage PR Review Threads
8+
9+
Use this skill when you need to inspect unresolved review threads and then reply to or resolve them.
10+
11+
## List unresolved review threads
12+
13+
```bash
14+
bunx @willbooster/agent-skills@latest list-pr-review-threads
15+
```
16+
17+
## Reply to and resolve review threads
18+
19+
```bash
20+
bunx @willbooster/agent-skills@latest resolve-pr-review-threads <<'EOF'
21+
{
22+
"replies": {
23+
"PRRT_kwDORiWJ-851nXBt": "Fixed in the latest update.",
24+
"PRRT_kwDORiWJ-851nXBu": "Kept as-is intentionally. Added clarification in the code."
25+
}
26+
}
27+
EOF
28+
```
29+
30+
The JSON object must contain `replies`, keyed by review thread ID.
31+
32+
## Notes
33+
34+
- Run the commands from the repository that owns the pull request you want to inspect.
35+
- `resolve-pr-review-threads` depends on thread IDs returned by `list-pr-review-threads`.

‎.agents/skills/open-pr/SKILL.md‎

Lines changed: 39 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,39 @@
1+
---
2+
name: open-pr
3+
description: Create a pull request for the current branch in the current repository.
4+
allowed-tools: Bash(bun:*), Bash(gh:*), Bash(git:*)
5+
---
6+
7+
# Open PR
8+
9+
Commit your changes and push them to the current branch.
10+
Write a PR body that helps reviewers quickly understand the scope, motivation, and validation.
11+
Include the linked issue when applicable, a concise summary of the changes, the reasoning behind them, and how they were tested.
12+
Run the following command to open a pull request.
13+
Finally, report the PR URL.
14+
15+
```bash
16+
bunx @willbooster/agent-skills@latest open-pr <<'EOF'
17+
Close #<issue>
18+
19+
## Summary
20+
21+
- What changed
22+
- Key scope or affected area
23+
- Any notable tradeoff or limitation
24+
25+
## Why
26+
27+
- Problem being solved
28+
- Reason this approach was chosen
29+
30+
## Testing
31+
32+
- Exact commands run
33+
- Manual verification steps if relevant
34+
35+
## Notes (if needed)
36+
37+
- Breaking changes, rollout concerns, screenshots, or follow-up work
38+
EOF
39+
```

‎.agents/skills/plan-issue-claude/SKILL.md‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
---
2+
name: plan-issue-claude
3+
description: Run Claude Code planning via the CLI and report the planning results.
4+
allowed-tools: Bash(bunx:*)
5+
---
6+
7+
# Planning workflow
8+
9+
1. Run the following command from the repository root with 1 hour timeout: `bunx @willbooster/agent-skills@latest plan --agent claude`
10+
2. Report on the issue URL.

‎.agents/skills/plan-issue-codex/SKILL.md‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
---
2+
name: plan-issue-codex
3+
description: Run Codex planning via the CLI and report the planning results.
4+
allowed-tools: Bash(bunx:*)
5+
---
6+
7+
# Planning workflow
8+
9+
1. Run the following command from the repository root with 1 hour timeout: `bunx @willbooster/agent-skills@latest plan --agent codex`
10+
2. Report on the issue URL.

‎.agents/skills/plan-issue-gemini/SKILL.md‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
---
2+
name: plan-issue-gemini
3+
description: Run Gemini CLI planning via the CLI and report the planning results.
4+
allowed-tools: Bash(bunx:*)
5+
---
6+
7+
# Planning workflow
8+
9+
1. Run the following command from the repository root with 1 hour timeout: `bunx @willbooster/agent-skills@latest plan --agent gemini`
10+
2. Report on the issue URL.

0 commit comments

Comments
 (0)