Conversation
…ields Agent-Logs-Url: https://github.com/verkyyi/github-agent-runner/sessions/338d3482-d23c-4130-9037-10008463c5ca Co-authored-by: verkyyi <2718137+verkyyi@users.noreply.github.com>
Agent-Logs-Url: https://github.com/verkyyi/github-agent-runner/sessions/338d3482-d23c-4130-9037-10008463c5ca Co-authored-by: verkyyi <2718137+verkyyi@users.noreply.github.com>
There was a problem hiding this comment.
Pull request overview
This PR completes two previously stubbed pieces of the sidekick plugin by filling in the curated workflow catalog and replacing TBD placeholders in the plugin manifest with real author/repo metadata.
Changes:
- Populated
skills/discover/catalog.mdwith 7 curated workflows (source, purpose, fit signals, friction, auth requirement). - Updated
.claude-plugin/plugin.jsonto replaceTBDauthor/homepage/repository values withverkyyi/github-agent-runner.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
skills/discover/catalog.md |
Replaces the stub template with 7 curated workflow entries and guidance about auth. |
.claude-plugin/plugin.json |
Fills in author and repo URLs that were previously TBD. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| 7 hand-picked entries from [`githubnext/agentics`](https://github.com/githubnext/agentics/tree/main/workflows). | ||
| All require Claude auth — see `../install/auth.md` for the OAuth vs API-key decision. |
There was a problem hiding this comment.
The catalog’s setup-friction blurbs don’t mention the extra OAuth-only post-compile .lock.yml tweak required by the documented install flow (skills/install/SKILL.md + skills/install/auth.md). As written, a reader could assume “one secret” is sufficient regardless of auth path. Consider noting here that the listed friction assumes the API-key path, and that the OAuth path adds the mandatory lockfile patch step (and re-application after any recompile).
| - **Upstream source**: `githubnext/agentics/workflows/issue-triage.md` | ||
| - **One-line purpose**: Labels new issues, detects spam, and posts an analysis comment with debugging tips and reproduction steps — automatically, the moment an issue lands. | ||
| - **Fits repos that**: receive issues regularly; have a label set already defined; maintainers who are time-poor and want triage handled before they even look at their inbox. | ||
| - **Setup friction**: low — one secret (Claude auth), no YAML to edit; customize the prompt body after install if you want custom label logic. |
There was a problem hiding this comment.
“No YAML to edit” is inaccurate for the OAuth auth path described in ../install/auth.md, which requires patching the generated .lock.yml after gh aw add. Consider rephrasing to something like “no workflow YAML to author by hand” or explicitly calling out the OAuth-only lockfile tweak.
| - **Setup friction**: low — one secret (Claude auth), no YAML to edit; customize the prompt body after install if you want custom label logic. | |
| - **Setup friction**: low — one secret (Claude auth), no workflow YAML to author by hand; customize the prompt body after install if you want custom label logic. |
The discover catalog moved from empty stub to 7 curated entries. Update README and CONTRIBUTING to reflect current state: - README: add catalog workflow table under /sidekick:discover; mark Publishing step 1 done; remove stale "catalog intentionally empty" note - CONTRIBUTING: drop "stub pending curation" language; fix catalog entry template heading level (### → ##) to match actual catalog format Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- README.md repository layout: catalog.md comment still said "stub until scope-lock"; updated to "(7 entries)" to match reality after PR #7 populated the catalog. - CONTRIBUTING.md Workflow files section said "six dogfooded workflows"; the repo has always had seven (repo-assist, daily-plan, update-docs, q, markdown-linter, pr-nitpick-reviewer, weekly-research) — corrected to "seven", consistent with README line 14. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- repo-assist trigger was missing the 👀 (eyes) reaction that the workflow frontmatter declares alongside /repo-assist and the schedule - catalog.md repository-layout comment still read "(stub until scope-lock)" after the catalog was populated with 7 entries in PR #7 - Prerequisites section for fork maintainers didn't mention GitHub Discussions must be enabled; daily-plan (announcements category) and weekly-research (ideas category) both require it Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- repo-assist trigger was missing the 👀 (eyes) reaction that the workflow frontmatter declares alongside /repo-assist and the schedule - catalog.md repository-layout comment still read "(stub until scope-lock)" after the catalog was populated with 7 entries in PR #7 - Prerequisites section for fork maintainers didn't mention GitHub Discussions must be enabled; daily-plan (announcements category) and weekly-research (ideas category) both require it Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
PR #7 replaced the TBD placeholders in plugin.json (author.name, homepage, repository) with real values. PR #8 struck through step 1 of the publishing checklist but missed step 2. Mark it done. Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
The
sidekickplugin shipped with two unfilled stubs:plugin.jsoncarriedTBDplaceholders for author and repo URLs, andskills/discover/catalog.mdwas an empty template with a TODO dated 2026-04-19.plugin.jsonauthor.name,homepage,repository→verkyyi/github-agent-runnerskills/discover/catalog.mdReplaced the stub with 7 hand-picked entries from
githubnext/agentics, each capturing upstream source, one-line purpose, fit signals, setup friction, and auth requirement:issue-triagepr-nitpick-reviewer/nitslash commandmarkdown-linterpr-fix/pr-fixslash commandweekly-issue-summarydaily-malicious-code-scandaily-repo-statusAll entries use
auth requirement: either— compatible with both subscription OAuth and API key paths documented inskills/install/auth.md.