All authors
Claude Skills by yoshpy-dev
github.com/yoshpy-dev27 skills0 installs43 views
- Anti BottleneckLoad this skill BEFORE asking the user for confirmation, approval, next steps, or choices that can be resolved through verification, repo context, or reasonable defaults. Also load when you are unsure how to proceed and might otherwise stop early.Votes: 0GitHub stars: 6
- Audit HarnessAudit the harness itself for drift, weak spots, overgrown instructions, missing deterministic checks, or language-pack gaps. Invoke automatically when harness-level changes accumulate and need consistency review.Votes: 0GitHub stars: 6
- Cross ReviewOptional cross-model second opinion on the current diff. Calls the CLI other than the one currently driving (Claude → Codex; Codex → Claude). Runs inline in the main context (not delegated as subagent) after /sync-docs completes. If the reviewer CLI is unavailable, silently skips and proceeds to /pr. Findings are triaged by the driving CLI using implementation context before presentation to the user.Votes: 0GitHub stars: 6
- ImplementExecute an approved plan in small coherent slices from an isolated task worktree, updating progress, evidence, and docs as implementation evolves. Invoke automatically after an approved plan exists and the task worktree is ready.Votes: 0GitHub stars: 6
- OrgLeader's operating manual for the org runtime. Use it to organize, oversee, and disband an org (its seats). Auto-invoked when promoting the current session to Leader to organize seats, or when the headless leader (`ralph org start`) needs its operating procedure.Votes: 0GitHub stars: 6
- PlanCreate or refresh a scoped implementation plan before risky, ambiguous, long-running, or multi-file work. Accepts an optional GitHub issue number or URL for context pre-fill. Resolves high-leverage implementation forks with the user before finalizing. Ensures a clean-base task worktree before writing plan artifacts. Shows a visual review page and asks the user to approve the plan before /implement.Votes: 0GitHub stars: 6
- PrCreate a pull request after self-review, verify, and test pass. Handles branch push, PR creation, plan archiving, and hand-off. Invoke automatically after /cross-review completes (or is skipped), when self-review, verify, and test reports all exist with passing verdicts.Votes: 0GitHub stars: 6
- ReleaseCut a new release tag so `brew upgrade ralph` picks up the latest build. Verifies main/clean state, runs the verify script, picks a semver bump, pushes the tag, monitors the Release workflow, and confirms the Homebrew tap was updated. Manual trigger only. Repo-specific — not distributed via template.Votes: 0GitHub stars: 6
- Self ReviewSelf-review the diff for code quality before formal verification. Covers naming, readability, unnecessary changes, typos, null safety, debug code, secrets, exception handling, security, and maintainability. Invoke automatically after /implement completes or when significant code changes are staged.Votes: 0GitHub stars: 6
- SpecTurn vague ideas or abstract prompts into detailed, actionable specifications through a grill-me-style decision-tree questioning loop with recommended answers, codebase exploration, web research, and interactive clarification with the user. Invoke when a repository-change request is too vague or abstract for /plan — missing objective, scope, or acceptance criteria. Do not invoke for reviews, Q&A or explanations, execution of an existing plan, trivial fixes, or when the user explicitly request...Votes: 0GitHub stars: 6
- Sync DocsSync plans, docs, and instruction files after behavior, commands, contracts, or workflows change. Also covers harness-internal consistency after skill, hook, rule, or script changes. Invoked after /test and before /cross-review as the doc-maintainer agent; inline execution is only a dispatch-failure fallback.Votes: 0GitHub stars: 6
- TestRun behavioral tests (unit, integration, regression) and produce a test report. Tests must pass before PR creation. Invoke automatically after /verify completes.Votes: 0GitHub stars: 6
- VerifyVerify spec compliance and run static analysis for a change. Checks acceptance criteria, documentation drift, linters, and type checks. Does NOT run tests — that is /test. Invoke automatically after /self-review completes.Votes: 0GitHub stars: 6
- Audit HarnessAudit the harness itself for drift, weak spots, overgrown instructions, missing deterministic checks, or language-pack gaps. Invoke automatically when harness-level changes accumulate and need consistency review.Votes: 0GitHub stars: 6
- Cross ReviewOptional cross-model second opinion on the current diff. Calls the CLI other than the one currently driving (Claude → Codex; Codex → Claude). Runs inline in the main context (not delegated as subagent) after /sync-docs completes. If the reviewer CLI is unavailable, silently skips and proceeds to /pr. Findings are triaged by the driving CLI using implementation context before presentation to the user.Votes: 0GitHub stars: 6
- ReleaseCut a new release tag so `brew upgrade ralph` picks up the latest build. Verifies main/clean state, runs the verify script, picks a semver bump, pushes the tag, monitors the Release workflow, and confirms the Homebrew tap was updated. Manual trigger only. Repo-specific — not distributed via template.Votes: 0GitHub stars: 6
- Self ReviewSelf-review the diff for code quality before formal verification. Covers naming, readability, unnecessary changes, typos, null safety, debug code, secrets, exception handling, security, and maintainability. Invoke automatically after /implement completes or when significant code changes are staged.Votes: 0GitHub stars: 6
- Sync DocsSync plans, docs, and instruction files after behavior, commands, contracts, or workflows change. Also covers harness-internal consistency after skill, hook, rule, or script changes. Invoked after /test and before /cross-review as the doc-maintainer agent; inline execution is only a dispatch-failure fallback.Votes: 0GitHub stars: 6
- TestRun behavioral tests (unit, integration, regression) and produce a test report. Tests must pass before PR creation. Invoke automatically after /verify completes.Votes: 0GitHub stars: 6
- VerifyVerify spec compliance and run static analysis for a change. Checks acceptance criteria, documentation drift, linters, and type checks. Does NOT run tests — that is /test. Invoke automatically after /self-review completes.Votes: 0GitHub stars: 6
- Archive- Status: PR created (#202), awaiting CI and merge - Owner: Claude Code - Date: 2026-10-05 - Related request: work スキルの名称を implement スキル(もしくは短縮形)に変更したい(2026-10-05 ユーザー依頼) - Related issue: N/A - Type: refactor - Branch: refactor/rename-work-skillVotes: 0GitHub stars: 6
- Reports- Date: 2026-10-05 - Plan: docs/plans/active/2026-10-05-rename-work-skill.md - Base branch: main - Driver: claude - Reviewer: codex - Triager: Claude Code (main context) - Reviewer status: complete - Self-review cross-ref: yes - Cycle: 1/2 - Total reviewer findings: 0 - After triage: ACTION_REQUIRED=0, WORTH_CONSIDERING=0, DISMISSED=0Votes: 0GitHub stars: 6
- Reports- Date: 2026-10-05 - Plan: docs/plans/active/2026-10-05-rename-work-skill.md - Branch: refactor/rename-work-skill(base main 4a5d7071、HEAD 7bfe76bc) - Reviewer: reviewer subagent (Claude)、cycle 1 - Scope: diff の品質だけ(命名、読みやすさ、不要な変更、過剰置換、root と template の不整合、コメントの正確さ、Go の `detectFlow` と追加テスト)。対象は `git diff main...HEAD`(71 ファイル、+389/-161)。plan の記録コミット(797d0551、7bfe76bc)は plan 本文を読んだが、差分の指摘対象にしていない。仕様への適合、テストの網羅、文書のずれは /verify・/test・/sync-docs の担当。テストと静的解析は実行していないVotes: 0GitHub stars: 6
- Reports- Date: 2026-10-05 - Plan: `docs/plans/active/2026-10-05-rename-work-skill.md` - Pipeline cycle: 1 of 2。差分は main の `4a5d7071` から branch HEAD `a627110e`(refactor/rename-work-skill)まで - 先行 report(それぞれを追加した commit): `docs/reports/self-review-2026-10-05-rename-work-skill.md`(`a8c137ec`。merge 可、F-1 は `2292014b` で修正済み)、 `docs/reports/verify-2026-10-05-rename-work-skill.md`(`4b050be6`。pass、LOW 1 件 V-1)、 `docs/reports/test-2026-10-05-rename-work-skill.md`(`a627110e`。pass)Votes: 0GitHub stars: 6
- Reports- Date: 2026-10-05 - Plan: docs/plans/active/2026-10-05-rename-work-skill.md - Tester: tester subagent (Claude)、pipeline cycle 1 - Scope: branch refactor/rename-work-skill の HEAD 4b050be6 と base main 4a5d7071 の差分(75 ファイル)。behavioral test だけを実行した(static analysis は /verify で済んでいる)。plan の AC7 と AC4、Test plan の regression と edge case を確かめた。Test plan の integration(AC5 / AC6)も、このブランチと main のバイナリを作り直して再実行した - Evidence: `docs/evidence/test-2026-10-05-rename-work-skill.log`(`docs/evidence/*.log` は git...Votes: 0GitHub stars: 6
- Reports- Date: 2026-10-05 - Plan: docs/plans/active/2026-10-05-rename-work-skill.md - Verifier: verifier subagent (Claude)、cycle 1 - Scope: 仕様への適合(AC1〜AC7、AC2b / AC2c を含む)、静的解析、文書のずれ。対象は `git diff main...HEAD`(base main 4a5d7071、HEAD 2292014b、74 ファイル)。plan の Evidence 節は信用せず、AC1〜AC3 と AC5 / AC6 はこの検証で再実行した。テスト(`go test` / `./scripts/run-test.sh`)は /test の担当なので実行していない - Evidence: `docs/evidence/verify-2026-10-05-rename-work-skill.log`(`docs/evidence/*.log` は gitignore 対象なので、手元にだけ残る)Votes: 0GitHub stars: 6
- Reports- Date: 2026-10-05 - Plan: docs/plans/archive/2026-10-05-rename-work-skill.md(この PR の最後のコミットで archive に移す) - Branch: refactor/rename-work-skill(base main 4a5d7071) - Diff: plan・報告・insight を除くと 71 files、+240 / -169。うち Go が 5 files で +79 / -15、埋め込みの雛形(`templates/`)が 30 files で +69 / -69Votes: 0GitHub stars: 6