all publishers

shakacode

@shakacode source repo

72 published skills

  1. ▌
    Docs 2 · shakacode bundle
    Generate, audit, or update project documentation to a professional open-source standard. Use this skill whenever the user mentions docs, documentation, README, API reference, guides, migration guides, troubleshooting, llms.txt, doc audit, or wants to improve any written developer-facing content in a repository. Also trigger when the user says things like "document this", "write docs for", "update the docs", "our docs need work", or compares documentation quality to other projects. Covers Ruby (YARD), TypeScript (TSDoc/JSDoc), Markdown guides, configuration references, and doc site structure.
    5.2k repo stars
  2. ▌
    Ab Servers 2 · shakacode
    How to drive shaka-perf twin-servers (the control + experiment Docker pair) from an agent — which subcommand to use for build, start containers, start the app, stop, run a command inside a side, or sync code changes. Bare `shaka-perf servers` is for humans (interactive menu); agents must call subcommands directly. Use whenever you need to bring twin-servers up, restart them after a change, or run something inside a container. Triggers include "servers", "twin servers", "ab servers", "control/experiment server", "run X in container", "ab tests failing".
    5.2k repo stars
  3. ▌
    Discover Abtests 2 · shakacode bundle
    Crawl a website and auto-generate .abtest.ts files for shaka-perf visreg visual regression testing. Use this skill whenever the user wants to discover, generate, or scaffold AB tests for a URL — even if they just say "set up tests for localhost:3020", "generate tests for this site", or "create visreg tests". Only use this skill when having no access to sources. When sources are present, use shaka-perf-add-coverage and shaka-perf-coverage instead.
    5.2k repo stars
  4. ▌
    Assess Abtest Quality 2 · shakacode
    Audit existing .abtest.ts files plus the latest `shaka-perf audit` results for anti-patterns, false-positive PASSes (blank/high-whitespace screenshots), and coverage gaps. Use whenever the user wants to review, audit, improve, or "assess quality" of AB tests — phrasings like "are my visreg tests any good?", "check the ab tests", "why is this test passing?", or "make these tests more reliable".
    5.2k repo stars
  5. ▌
    Setup Docker Servers For Ab Tests 2 · shakacode bundle
    setup-docker-servers-for-ab-tests
    5.2k repo stars
  6. ▌
    Stress Test 2 · shakacode
    Orchestrate a destructive demo-workspace QA stress test for React on Rails leakage, memory, performance, security, and framework edge cases. Use only when the user explicitly asks to run stress testing.
    5.2k repo stars
  7. ▌
    Rsc Adoption 2 · shakacode
    Use when adopting React Server Components in a React on Rails Pro app, including prerequisites, generator setup, component boundaries, data flow, and safety checks.
    5.2k repo stars
  8. ▌
    Doctor Fix Loop 2 · shakacode
    Use when diagnosing a React on Rails app with the stable doctor JSON contract and iterating through actionable remediation until no error-level checks remain.
    5.2k repo stars
  9. ▌
    Streaming Debug 2 · shakacode
    Use when a React on Rails Pro streaming SSR or async-props response buffers, stalls, fails to reveal Suspense content, or behaves differently behind a proxy.
    5.2k repo stars
  10. ▌
    Install And Upgrade 2 · shakacode
    Use when installing React on Rails into an existing Rails app or upgrading its gem, npm package, generated configuration, and lockfiles without version skew.
    5.2k repo stars
  11. ▌
    Review Architecture · shakacode
    Use when reviewing or designing shaka-perf framework extension points, pipeline or stage variants, artifact ownership, report serialization boundaries, or name-keyed behavior dispatch.
    5.2k repo stars
  12. ▌
    Shaka Perf Coverage · shakacode bundle
    Use to check if there are A/B tests for some scenario. Load this skill when asked about performance and visual regression testing.
    5.2k repo stars
  13. ▌
    Troubleshoot Abtest · shakacode
    Debug ONE failing shaka-perf test at ONE viewport by attaching to its live browser — no MCP, no install. `shaka-perf troubleshoot` freezes the visreg + perf browsers open on the failing page; its own subcommands attach over CDP to inspect them. Use whenever a visreg mismatch or perf run needs eyes on the actual page — "why is this test failing", "look at the live page", "debug this abtest", "attach to the troubleshoot browser", "inspect the control vs experiment DOM".
    5.2k repo stars
  14. ▌
    Shaka Perf Add Coverage · shakacode
    Use when source code is available and the user asks to add ShakaPerf A/B tests or improve A/B tests coverage for specified UI components or rendered states. Also use when asked to deduplicate A/B tests. Also use when asked to measure FE performance.
    5.2k repo stars
  15. ▌
    Run E2e · shakacode
    Run repo end-to-end checks through scripts/e2e/run.sh for webpack, rspack, or both bundlers.
    5.2k repo stars
  16. ▌
    Rsc Triage · shakacode
    Refresh internal/docs/open-rsc-work-status.md from live react_on_rails_rsc GitHub issue and PR state, using UNKNOWN for facts that cannot be verified.
    5.2k repo stars
  17. ▌
    Stress Test · shakacode
    Orchestrate a destructive demo-workspace QA stress test for React on Rails leakage, memory, performance, security, and framework edge cases. Use only when the user explicitly asks to run stress testing.
    5.2k repo stars
  18. ▌
    React Upgrade · shakacode
    Legacy helper for emergency maintenance of the vendored react-server-dom-webpack runtime through scripts/react-upgrade/upgrade.js and the React fork cherry-pick workflow.
    5.2k repo stars
  19. ▌
    Downstream E2e · shakacode
    Run downstream integration checks through scripts/e2e/downstream.sh when it exists, or report the current #59 blocker stub.
    5.2k repo stars
  20. ▌
    Verify Release · shakacode
    Verify release packaging for react-on-rails-rsc with yarn verify:artifacts / scripts/verify-release.sh.
    5.2k repo stars
  21. ▌
    Rsc Verify Pr Fix · shakacode
    Manually verify a react-on-rails-rsc bug-fix PR by reproducing the failure before the fix and confirming the same RSC/plugin signal passes after.
    5.2k repo stars
  22. ▌
    Rsc Update Changelog · shakacode
    Update react-on-rails-rsc CHANGELOG.md and optional package version headers for npm release or prerelease workflows.
    5.2k repo stars
  23. ▌
    Rsc Guardrails · shakacode
    Use when adding, editing, or reviewing React Server Components (RSC) code in React on Rails or React on Rails Pro — inline payload injection and streaming, the Node renderer, client-reference/manifest resolution, RSC controllers and routes, or props/console/error serialization. Covers the security and cross-request-isolation invariants that RSC changes must not regress.
    5.2k repo stars
  24. ▌
    Rsc Adoption · shakacode
    Use when adopting React Server Components in a React on Rails Pro app, including prerequisites, generator setup, component boundaries, data flow, and safety checks.
    5.2k repo stars
  25. ▌
    Run Fleet Validation · shakacode bundle
    Generate and coordinate the complete React on Rails release fleet lifecycle or public-only standing-health evidence from internal/contributor-info/demo-fleet.yml. Use when a maintainer wants to validate an RC/beta/final, inspect fleet currency/default health, split release work across machines, or run fail-closed closeout.
    5.2k repo stars
  26. ▌
    Doctor Fix Loop · shakacode
    Use when diagnosing a React on Rails app with the stable doctor JSON contract and iterating through actionable remediation until no error-level checks remain.
    5.2k repo stars
  27. ▌
    Streaming Debug · shakacode
    Use when a React on Rails Pro streaming SSR or async-props response buffers, stalls, fails to reveal Suspense content, or behaves differently behind a proxy.
    5.2k repo stars
  28. ▌
    Optimize Rsc Performance · shakacode
    Use when planning, implementing, validating, or reviewing React Server Components (RSC) page performance optimization in React on Rails or React on Rails Pro work. Guides agents through clean baseline/control setup, one-change experiments, visual parity checks, performance measurement, package-stack discipline, artifact recording, and PR evidence for RSC static pages.
    5.2k repo stars
  29. ▌
    Install And Upgrade · shakacode
    Use when installing React on Rails into an existing Rails app or upgrading its gem, npm package, generated configuration, and lockfiles without version skew.
    5.2k repo stars
  30. ▌
    React On Rails Update Changelog · shakacode
    React on Rails release-train changelog updates, including target=release and release/X.Y.Z PR targeting while the portable update-changelog skill remains mainline-only.
    5.2k repo stars
  31. ▌
    React On Rails Release Train Issue Evaluation · shakacode bundle
    Use when evaluating React on Rails GitHub issues for release-train targeting, especially deciding whether new, follow-up, or non-started issues belong on release/17.0.0, another release/X.Y.Z branch, or main.
    5.2k repo stars
  32. ▌
    Ab Servers · shakacode
    How to drive shaka-perf twin-servers (the control + experiment Docker pair) from an agent — which subcommand to use for build, start containers, start the app, stop, run a command inside a side, or sync code changes. Bare `shaka-perf servers` is for humans (interactive menu); agents must call subcommands directly. Use whenever you need to bring twin-servers up, restart them after a change, or run something inside a container. Triggers include "servers", "twin servers", "ab servers", "control/experiment server", "run X in container", "ab tests failing".
    5.2k repo stars
  33. ▌
    Discover Abtests · shakacode bundle
    Crawl a website and auto-generate .abtest.ts files for shaka-perf visreg visual regression testing. Use this skill whenever the user wants to discover, generate, or scaffold AB tests for a URL — even if they just say "set up tests for localhost:3020", "generate tests for this site", or "create visreg tests".
    5.2k repo stars
  34. ▌
    Assess Abtest Quality · shakacode
    Audit existing .abtest.ts files plus the latest `shaka-perf audit` results for anti-patterns, false-positive PASSes (blank/high-whitespace screenshots), and coverage gaps. Use whenever the user wants to review, audit, improve, or "assess quality" of AB tests — phrasings like "are my visreg tests any good?", "check the ab tests", "why is this test passing?", or "make these tests more reliable".
    5.2k repo stars
  35. ▌
    Setup Docker Servers For Ab Tests · shakacode bundle
    setup-docker-servers-for-ab-tests
    5.2k repo stars
  36. ▌
    Tdd · shakacode bundle
    Drive a portable red-green-refactor workflow for features, bug fixes, and changes to existing behavior. Use when implementing behavior with test-driven development, reproducing a bug as a failing test before fixing it, changing the semantics of existing code, or when the user asks for TDD, test-first, or red-green-refactor discipline.
    5.2k repo stars
  37. ▌
    Spec · shakacode bundle
    Use when an implementation request is vague, high-ambiguity, or needs requirements, design, and executable tasks before plan-pr-batch or pr-batch.
    5.2k repo stars
  38. ▌
    Pause · shakacode bundle
    Print restart-safe copy-paste prompts for pausing an agent thread before restarting Codex, Claude, or another runner and for resuming in the same thread or a new chat from the handoff. Use when the user asks for a pause prompt, restart prompt, resume-after-restart prompt, new-chat restart prompt, or operator handoff prompts for non-batch or PR-batch agent work.
    5.2k repo stars
  39. ▌
    Run CI · shakacode bundle
    Analyze current branch changes with the repo CI detector and run user-selected local CI jobs. Use when the user asks to run, reproduce, or choose local CI checks.
    5.2k repo stars
  40. ▌
    Status · shakacode bundle
    Report tight progress on the current work - done, in progress, blocked, and next - without starting new work. Use when asked for a status update or "where are we / anything needed from me".
    5.2k repo stars
  41. ▌
    Triage · shakacode bundle
    Generate a whole-surface issue/PR inventory, dependency graph, and capacity-aware pr-batch split from live GitHub plus coordination-backend state. Use when a coordinator needs current issue/PR inventory and batch planning.
    5.2k repo stars
  42. ▌
    Verify · shakacode bundle
    Run a local verification loop for the current branch before creating or updating a PR, selecting checks from the repo's binstub contract and changed files. Use when asked to verify, test, or prepare PR changes.
    5.2k repo stars
  43. ▌
    Continue · shakacode bundle
    Resume an in-progress task with a structured checkpoint instead of a bare "continue", re-establishing what is done, what is next, and how done is verified. Use when resuming work after an interruption, handoff, or a vague "keep going".
    5.2k repo stars
  44. ▌
    Pr Batch · shakacode bundle
    Plan and safely run one or more canonical issue, existing PR, or durably overridden ad-hoc work lanes with coordinated subagents, validation, review, and merge-readiness. Unbound direct prompts route through planning/reconciliation before implementation launch. Use when coordinating one or more implementation lanes.
    5.2k repo stars
  45. ▌
    QA Stress · shakacode
    Use when explicitly asked to run destructive QA stress testing against repo-owned demo or target apps, especially for leakage, memory growth, performance degradation, hostile inputs, fault injection, pentesting, and gated finding reports.
    5.2k repo stars
  46. ▌
    Autoreview · shakacode bundle
    Run a structured second-model code review as a closeout gate on a local, branch, or commit diff, then verify every finding against the real code and loop until clean. Use before commit/push/ship in this repo.
    5.2k repo stars
  47. ▌
    Audit Chats · shakacode bundle
    Audit multiple Codex tasks and visible ChatGPT chats for archive and follow-up actions, or recover interrupted Codex tasks when explicitly requested. Use for machine-wide cleanup and recovery after quota exhaustion or app restarts; use close-session or close-batch for one task.
    5.2k repo stars
  48. ▌
    Close Batch · shakacode bundle
    Recover and close stale or unfinished PR-batch tasks by resolving lifecycle ownership, continuing canonical closeout, walking the maintainer through current PRs or blockers, and archiving only after the archive gate passes. Use when a batch task has lingered, may have open or merged PRs, needs cleanup, or needs a read-only archive-readiness assessment. Do not use for ordinary lane-progress or batch-status snapshots; use $batch-status instead. Use $close-session for generic non-batch archive-readiness questions.
    5.2k repo stars
  49. ▌
    Plan Review · shakacode bundle
    Use when reviewing an implementation plan before coding or launching workers to check approach, scope, and repo-convention fit.
    5.2k repo stars
  50. ▌
    Batch Status · shakacode bundle
    Use when asked where a dispatched PR batch stands - mid-flight or after dispatch - to report per-lane coordination and live GitHub state in the canonical readiness vocabulary. Read-only; use close-batch for completed-batch closeout and pr-monitoring for a single PR.
    5.2k repo stars
  51. ▌
    Replicate CI · shakacode bundle
    Use when local validation is green but hosted CI is red, a CI-only failure needs reproduction, or runner/toolchain parity is suspected.
    5.2k repo stars
  52. ▌
    Close Session · shakacode bundle
    Close an active agent task with live-state verification, durable outcome capture, explicit follow-up ownership, and an archive-readiness verdict. Use when the user says "close session", asks "anything else pending?", "any decisions needed?", or "should we archive this chat?", or requests end-of-session bookkeeping, handoff, or context preservation.
    5.2k repo stars
  53. ▌
    Plan Pr Batch · shakacode bundle
    Use when choosing GitHub issues or PRs for a PR batch, recommending and grouping worker lanes by model/reasoning-effort assignment, preparing a subagent batch plan, or producing a ready goal prompt that invokes pr-batch.
    5.2k repo stars
  54. ▌
    Pr Monitoring · shakacode bundle
    Use when monitoring an opened pull request through current-head checks, comments, conflicts, merge-readiness, and final handoff.
    5.2k repo stars
  55. ▌
    Task Observer · shakacode bundle
    Optional meta-maintenance skill for recording sanitized observations that may improve shared skills or durable workflow lessons. Use only when the user explicitly asks for task observation, skill improvement capture, or observation review; do not activate it as a required gate for ordinary workflows.
    5.2k repo stars
  56. ▌
    Verify Pr Fix · shakacode bundle
    Manually verify that a bug-fix PR actually works by reproducing the failure before the fix and confirming it is gone after, with captured evidence, then posting findings to the PR (and optionally the linked issue). Use when asked to manually verify a PR/fix, reproduce an issue and its fix, confirm a fix works end to end, or capture screenshots or clips proving a change.
    5.2k repo stars
  57. ▌
    Address Review · shakacode bundle
    Fetch GitHub PR review comments, triage them into must-fix/discuss/optional/skipped, and guide fixing or replying to selected feedback. Use when addressing PR review comments or review threads.
    5.2k repo stars
  58. ▌
    Evaluate Issue · shakacode bundle
    Use before fixing, batching, or assigning GitHub issues or proposed fixes when the value is uncertain, the report came from AI/code analysis, the fix is complex, or the user asks whether an issue is worth doing. Produces an evidence-backed recommendation: fix now, document/work around, park, close, or ask for product input.
    5.2k repo stars
  59. ▌
    Manual Testing · shakacode bundle
    Use when verifying changed behavior in a real running app or service with recorded HTTP, browser, or CLI evidence, including acceptance criteria and cheap unhappy paths.
    5.2k repo stars
  60. ▌
    Pr Walkthrough · shakacode bundle
    Explain a pull request as a conceptual walkthrough, either interactively one change at a time or as one complete COMMENT-only GitHub review when explicitly requested. Use when a user asks to understand, explain, present, tour, or walk through a PR or diff; when a large or complex PR needs a reviewer-friendly guided tour; or when an `ask` merge-authority workflow requires human understanding before the final merge decision.
    5.2k repo stars
  61. ▌
    Fix Flaky Tests · shakacode bundle
    Use when a test fails intermittently in CI — classify the intermittency, work from the real CI error, fix the root cause systemically, and verify with a green CI build rather than local runs.
    5.2k repo stars
  62. ▌
    Post Merge Audit · shakacode bundle
    Use when auditing merged PRs after concurrent agent work, before a release candidate, after a suspected bad merge, or when checking for missed reviews, missing changelog entries, cross-PR interactions, or release risk.
    5.2k repo stars
  63. ▌
    Update Changelog · shakacode bundle
    Analyze merged PRs and update the changelog, optionally stamping release, rc, beta, or explicit version headers. Use before releases or when changelog entries are missing.
    5.2k repo stars
  64. ▌
    Plan Issue Triage · shakacode bundle
    Use when preparing a ready prompt for Claude, Codex, or another agent to perform a review-only GitHub issue triage or open-issue audit, especially broad scans such as all current issues, unlabeled issues, performance-regression clusters, close candidates, or customer-feedback parked work.
    5.2k repo stars
  65. ▌
    Structural Review · shakacode bundle
    Use when a diff is correct but may still be making the codebase worse — file growth, scattered conditionals, thin abstractions, layer violations, or feature-flag branching debt.
    5.2k repo stars
  66. ▌
    Type Design Review · shakacode bundle
    Use when reviewing data models, signatures, domain types, parsing, casts, or state machines so invalid states stay hard to represent.
    5.2k repo stars
  67. ▌
    Adversarial Pr Review · shakacode bundle
    Use when a PR needs skeptical pre-merge or post-merge risk review, especially after concurrent agent work, before merge readiness, before a release candidate, or when Codex or Claude should red-team correctness, security, compatibility, changelog, validation, and review-gate risks.
    5.2k repo stars
  68. ▌
    Secure Github Actions · shakacode bundle
    Audit GitHub Actions workflows and composite actions for expression injection, broad reusable-workflow secret inheritance, mutable or undocumented external references, and actions outside a closed trusted allowlist. Use when assessing GitHub Actions trust boundaries.
    5.2k repo stars
  69. ▌
    Benchmark Verification · shakacode bundle
    Use when verifying performance-sensitive changes with baseline-vs-patched benchmark evidence, repeated runs, noise-aware verdicts, and repo-seam benchmark commands.
    5.2k repo stars
  70. ▌
    Restart Codex Subagents · shakacode bundle
    Prepare or recover Codex tasks and subagents around an app restart, crash, or account change. Use when preparing for a restart or recovering from checkpoints, logs, and live state when no handoff exists.
    5.2k repo stars
  71. ▌
    Untrusted Contributor Intake · shakacode bundle
    Safely assess an outside-contributor fork pull request through metadata and diff evidence, then report a maintainer decision without executing untrusted content. Use when screening an outside-contributor fork pull request.
    5.2k repo stars
  72. ▌
    Docs · shakacode bundle
    Generate, audit, or update project documentation to a professional open-source standard. Use this skill whenever the user mentions docs, documentation, README, API reference, guides, migration guides, troubleshooting, llms.txt, doc audit, or wants to improve any written developer-facing content in a repository. Also trigger when the user says things like "document this", "write docs for", "update the docs", "our docs need work", or compares documentation quality to other projects. Covers Ruby (YARD), TypeScript (TSDoc/JSDoc), Markdown guides, configuration references, and doc site structure.
    5.2k repo stars