dyoshikawa
- 39 skills
- 0 followers
- 1 week ago last updated
- ▌ Rulesync Feature Research · dyoshikawa bundleMaps rulesync feature implementations to upstream coding-agent documentation. Use when evaluating rulesync issues, comparing any coding-agent client with rulesync source capability surfaces, checking support, or planning a client map.
- ▌ Porting Another Repository · dyoshikawaPlan how to port a feature, configuration, or implementation from this repository into another repository. Analyzes the source feature here and the target repo's conventions, then writes a multi-file porting plan (overview, source analysis, target analysis, plan, diff) to tmp/porting-another-repository-{YYYYMMDD-HHmm}/*.md for the user to review and apply manually.
- ▌ Create Issue With Websearch · dyoshikawaCreate a GitHub issue from a vague idea by thoroughly researching the topic on the web to sharpen the specification before filing
- ▌ Draft Issue To External Repository · dyoshikawaDraft a GitHub issue targeting a third-party repository (outside this project's owner). Researches the target repo's conventions and the topic in depth, iterates with the user on scope and tone, and produces a final body saved to tmp/external-repository-issues/*.md for the user to post manually when gh auth lacks permission on the target.
- ▌ Batch Review Prs Awaiting Maintainer · dyoshikawaBatch-triage open pull requests: list PRs with prs-awaiting-maintainer, review each with review-pr, then post-review-comments when there are merge-blocker findings, or create-scrap-issue for non-blocking findings and merge-pr when there are none. Use when the user wants to review and resolve a batch of PRs in one pass.
- ▌ Rulesync · dyoshikawaGenerates and syncs AI rule configuration files (.cursorrules, CLAUDE.md, copilot-instructions.md) across 20+ coding tools from a single source. Use when syncing AI rules, running rulesync commands, importing or generating rule files, or managing shared AI coding configurations.
- ▌
- ▌ Goal Pr · dyoshikawaDrive a pull request to a clean state and merge it: run the `review-pr` skill, fix every mid-or-above finding, and repeat until no mid-or-above findings remain, then merge. Use when the user wants to finish a PR by reviewing, fixing, and merging it, or triggers on "the `goal-pr` skill".
- ▌
- ▌ Pull Main · dyoshikawaSwitch to main branch and pull latest changes with prune. Use when the user wants to pull latest main, update main, or sync main with remote.
- ▌ Review Pr · dyoshikawaReview a pull request for code quality and security issues. Use when the user wants to review a PR, check PR code changes, or audit a pull request. Triggers on: "review PR", "review pull request", "check this PR", "the `review-pr` skill".
- ▌ Agent Team · dyoshikawaForm an Agent Team of Implementer and Reviewer subagents to tackle the given task, looping implementation and review until the Reviewer reports zero high-or-above findings and no more than three mid findings.
- ▌
- ▌ Create Issue · dyoshikawaCreate a GitHub issue with detailed description, purpose, and appropriate labels
- ▌ Diff Analyze · dyoshikawaAnalyze the differences between the current branch and origin/main, and summarize the current work progress
- ▌ Goal Release · dyoshikawaCut a release end to end: use the `draft-release` skill to open the release PR and draft GitHub release, wait for CI to turn green, run the `merge-pr` skill to merge the release PR, then update the Homebrew formula from the published release assets. Use when the user wants to draft and merge a release in one go, or triggers on "the `goal-release` skill".
- ▌
- ▌ Triage Issues · dyoshikawaTriage open GitHub issues by reviewing unlabeled ones and applying the most appropriate labels based on their content
- ▌ Clean Branches · dyoshikawaClean up unnecessary local branches and prune stale remote-tracking branches
- ▌ Commit Push Pr · dyoshikawaCommit current changes, push to remote, and create or update a pull request. Use when the user wants to commit and create a PR, push changes and open a pull request, or ship their current work as a PR.
- ▌ Playwright CLI · dyoshikawa bundleAutomate browser interactions, test web pages and work with Playwright tests.
- ▌ Review Pr Lite · dyoshikawaReview a pull request for code quality and security issues without using subagents. Use when the user wants a lighter-weight PR review in a single skill.
- ▌ Release Dry Run · dyoshikawaDry run for release: summarize changes since last release and suggest version bump.
- ▌ Batch All Issues · dyoshikawaResolve every open issue one at a time: fact-check each with web research, close the ones that need no action, and run the `goal-pr` skill to fix, review, and merge the ones that do — repeating until no actionable issues remain.
- ▌ Create Scrap Issue · dyoshikawaCreate a GitHub issue that consolidates passed content into a single scrap issue with background context and solution details, labeled as maintainer-scrap. Use when the user wants to create a scrap issue, jot down notes as a GitHub issue, or save findings for later.
- ▌ Post Issue Comment · dyoshikawaPost a reply comment on a GitHub issue in English with a natural, concise writing style, based on the intent passed as arguments
- ▌ Rebase Latest Main · dyoshikawaFetch latest origin/main and rebase it onto the current branch, resolving conflicts if necessary. Use when the user wants to rebase on main, update their branch with latest main, or sync with upstream.
- ▌
- ▌ Git Worktree Runner · dyoshikawaManages git worktrees using git-worktree-runner (gtr). Use when the user needs to create, list, remove, or navigate worktrees with `git gtr` commands, open editors or AI tools in worktrees, manage parallel development branches, or check out GitHub PRs (including from forks) into worktrees.
- ▌ Opencode Gpt Review · dyoshikawaRun the `review-full-pr` skill on another model (github-copilot/gpt-5.4) via opencode, then thoroughly investigate and vet the resulting findings, and present only the valid ones to the user.
- ▌ Prs Awaiting Author · dyoshikawaList open pull requests where the ball is in the author's court: CI is failing, review comments are unaddressed, or a maintainer question is awaiting the author's reply. Use when the user wants to see PRs awaiting author action.
- ▌ Post Review Comments · dyoshikawaPost line-level review comments and an overall review comment on a PR in English with a natural, concise writing style
- ▌ Resolve Scrap Issues · dyoshikawaFetch recent maintainer-scrap issues, validate each with web research, then either close the ones that need no action or open a single consolidated pull request that resolves the ones that do
- ▌ Babysit Dependabot Pr · dyoshikawaBabysit a Dependabot dependency-bump PR all the way to merge: verify the author is the genuine Dependabot bot, diagnose and resolve any CI failure (excluding or fixing a breaking bump when needed), get every check green, and merge. Use when the user wants to shepherd a Dependabot bump PR to merge.
- ▌ Research Tool Updates · dyoshikawaResearch recent upstream releases of every rulesync target tool, detect capabilities rulesync has not yet followed, file one GitHub issue per tool for the gaps, and scout popular or promising coding agents rulesync does not target yet.
- ▌ Batch All Scrap Issues · dyoshikawaResolve every open maintainer-scrap issue one at a time: fact-check each with web research, close the ones that need no action, and run the `goal-pr` skill to fix, review, and merge the ones that do — repeating until no actionable scrap issues remain.
- ▌ Goal Issues And Release · dyoshikawaClear the open issue backlog and then cut a release, in one autonomous run: use the `batch-all-issues` skill to resolve every open issue, then the `goal-release` skill to draft, merge, and see the release through publication. Never asks the user anything — every decision is made autonomously, and blockers are reported at the end instead of interrupting the run.
- ▌ Prs Awaiting Maintainer · dyoshikawaList open pull requests where the ball is in the maintainer's court: CI is green and the PR is ready for a maintainer to review, re-review, or merge. Use when the user wants to see PRs awaiting maintainer action.
- ▌ Understand Scrap Issues · dyoshikawaFetch the most recent maintainer-scrap issues (up to 3) and understand their content