Skip to content

Fix: Replace WebSearch with webfetch in brainstorm skill#12

Merged
striderZA merged 4 commits into
developmentfrom
fix/websearch
May 1, 2026
Merged

Fix: Replace WebSearch with webfetch in brainstorm skill#12
striderZA merged 4 commits into
developmentfrom
fix/websearch

Conversation

@striderZA

Copy link
Copy Markdown
Owner

Closes #7

@github-actions

github-actions Bot commented May 1, 2026

Copy link
Copy Markdown
Contributor

fatal: could not read Username for 'https://github.com': No such device or address

opencode session  |  github run

striderZA and others added 3 commits May 1, 2026 21:30
Changed permissions for contents from read to write and updated checkout action to persist credentials.
Changed persist-credentials to true and added GITHUB_TOKEN.
Co-authored-by: striderZA <striderZA@users.noreply.github.com>
@github-actions

github-actions Bot commented May 1, 2026

Copy link
Copy Markdown
Contributor

PR Review: fix/websearch → development

Overview

3 files changed, 6 additions, 4 deletions. Fixes a tool name mismatch and updates CI workflow configs.


Change 1: .opencode/skills/brainstorm/SKILL.mdWebSearchwebfetch

Verdict: ✅ Correct

  • WebSearch is not an available tool in OpenCode; webfetch is. This was a latent bug — any agent invoking this skill would fail with "unknown tool" when the allowed-tools frontmatter listed WebSearch. The fix resolves that.

Suggestion: The allowed-tools header on line 6 now reads Read, Glob, Grep, Write, webfetch, Task, AskUserQuestion. Consider alphabetizing for consistency with other skill files:

allowed-tools: AskUserQuestion, Glob, Grep, Read, Task, Write, webfetch

Change 2: .github/workflows/opencode-review.yml — Added model and prompt

Verdict: ✅ Functional, minor concerns

  • Adds model: opencode-go/deepseek-v4-flash and a prompt field with review instructions. This allows the opencode action to run autonomously without relying on GitHub defaults.

Issues:

  1. Mixing use_github_token: true with explicit secrets.GITHUB_TOKEN (line 30, 33). These may conflict. The action docs suggest use_github_token: true is sufficient — the duplicate GITHUB_TOKEN in env is unnecessary and could cause unexpected auth behavior.

  2. @latest tag (line 27) — mutable reference. If a new version of the action ships a breaking change, this workflow silently breaks. Recommend pinning to a commit SHA or semver tag like @v1.


Change 3: .github/workflows/opencode.yml — Added pull_request_review_comment trigger

Verdict: ✅ Correct

  • Adds pull_request_review_comment with types: [created] alongside existing issue_comment. This allows /oc or /opencode commands in PR review comments, which is the intended behavior.

Issue: The contents permission is read (line 20). If opencode needs to push comments or update PRs from review comment triggers, this may need write. Not a blocker for the current PR, but worth noting.


Summary

Category Count
✅ Approved 3/3 changes functional
⚠️ Minor issues @latest tag, redundant GITHUB_TOKEN, mixed token config
❌ Blockers None

The PR delivers what it promises: replaces a broken tool reference and improves CI configuration. The issues noted are non-blocking but should be addressed in a follow-up.

New%20session%20-%202026-05-01T19%3A30%3A58.776Z
opencode session  |  github run

@striderZA striderZA merged commit 75a49bc into development May 1, 2026
@striderZA striderZA deleted the fix/websearch branch May 2, 2026 07:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant