shakacode
- 62 skills
- 0 followers
- 6 hours ago last updated
- ▌ Review Architecture · shakacodeUse when reviewing or designing shaka-perf framework extension points, pipeline or stage variants, artifact ownership, report serialization boundaries, or name-keyed behavior dispatch.
- ▌ Shaka Perf Coverage · shakacode bundleUse to check if there are A/B tests for some scenario. Load this skill when asked about performance and visual regression testing.
- ▌ Troubleshoot Abtest · shakacodeDebug 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".
- ▌ Shaka Perf Add Coverage · shakacodeUse 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.
- ▌ Run E2e · shakacodeRun repo end-to-end checks through scripts/e2e/run.sh for webpack, rspack, or both bundlers.
- ▌ Rsc Triage · shakacodeRefresh 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.
- ▌ Stress Test · shakacodeOrchestrate 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.
- ▌ React Upgrade · shakacodeLegacy 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.
- ▌ Downstream E2e · shakacodeRun downstream integration checks through scripts/e2e/downstream.sh when it exists, or report the current #59 blocker stub.
- ▌ Verify Release · shakacodeVerify release packaging for react-on-rails-rsc with yarn verify:artifacts / scripts/verify-release.sh.
- ▌ Rsc Verify Pr Fix · shakacodeManually 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.
- ▌ Rsc Update Changelog · shakacodeUpdate react-on-rails-rsc CHANGELOG.md and optional package version headers for npm release or prerelease workflows.
- ▌ Rsc Guardrails · shakacodeUse 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.
- ▌ Rsc Adoption · shakacodeUse when adopting React Server Components in a React on Rails Pro app, including prerequisites, generator setup, component boundaries, data flow, and safety checks.
- ▌ Run Fleet Validation · shakacode bundleGenerate 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.
- ▌ Doctor Fix Loop · shakacodeUse when diagnosing a React on Rails app with the stable doctor JSON contract and iterating through actionable remediation until no error-level checks remain.
- ▌ Streaming Debug · shakacodeUse 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.
- ▌ Optimize Rsc Performance · shakacodeUse 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.
- ▌ Install And Upgrade · shakacodeUse when installing React on Rails into an existing Rails app or upgrading its gem, npm package, generated configuration, and lockfiles without version skew.
- ▌ React On Rails Update Changelog · shakacodeReact 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.
- ▌ React On Rails Release Train Issue Evaluation · shakacode bundleUse 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.
- ▌ Ab Servers · shakacodeHow 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".
- ▌ Discover Abtests · shakacode bundleCrawl 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".
- ▌ Assess Abtest Quality · shakacodeAudit 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".
- ▌
- ▌ Tdd · shakacode bundleDrive 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.
- ▌ Spec · shakacode bundleUse when an implementation request is vague, high-ambiguity, or needs requirements, design, and executable tasks before plan-pr-batch or pr-batch.
- ▌ Pause · shakacode bundlePrint 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.
- ▌ Run CI · shakacode bundleAnalyze 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.
- ▌ Status · shakacode bundleReport 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".
- ▌ Triage · shakacode bundleGenerate 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.
- ▌ Verify · shakacode bundleRun 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.
- ▌ Continue · shakacode bundleResume 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".
- ▌ Pr Batch · shakacode bundlePlan 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.
- ▌ QA Stress · shakacodeUse 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.
- ▌ Autoreview · shakacode bundleRun 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.
- ▌ Audit Chats · shakacode bundleAudit 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.
- ▌ Close Batch · shakacode bundleRecover 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.
- ▌ Plan Review · shakacode bundleUse when reviewing an implementation plan before coding or launching workers to check approach, scope, and repo-convention fit.
- ▌ Batch Status · shakacode bundleUse 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.
- ▌ Replicate CI · shakacode bundleUse when local validation is green but hosted CI is red, a CI-only failure needs reproduction, or runner/toolchain parity is suspected.
- ▌ Close Session · shakacode bundleClose 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.
- ▌ Plan Pr Batch · shakacode bundleUse 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.
- ▌ Pr Monitoring · shakacode bundleUse when monitoring an opened pull request through current-head checks, comments, conflicts, merge-readiness, and final handoff.
- ▌ Task Observer · shakacode bundleOptional 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.
- ▌ Verify Pr Fix · shakacode bundleManually 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.
- ▌ Address Review · shakacode bundleFetch 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.
- ▌ Evaluate Issue · shakacode bundleUse 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.
- ▌ Manual Testing · shakacode bundleUse 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.
- ▌ Pr Walkthrough · shakacode bundleExplain 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.
- ▌ Fix Flaky Tests · shakacode bundleUse 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.
- ▌ Post Merge Audit · shakacode bundleUse 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.
- ▌ Update Changelog · shakacode bundleAnalyze merged PRs and update the changelog, optionally stamping release, rc, beta, or explicit version headers. Use before releases or when changelog entries are missing.
- ▌ Plan Issue Triage · shakacode bundleUse 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.
- ▌ Structural Review · shakacode bundleUse 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.
- ▌ Type Design Review · shakacode bundleUse when reviewing data models, signatures, domain types, parsing, casts, or state machines so invalid states stay hard to represent.
- ▌ Adversarial Pr Review · shakacode bundleUse 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.
- ▌ Secure Github Actions · shakacode bundleAudit 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.
- ▌ Benchmark Verification · shakacode bundleUse when verifying performance-sensitive changes with baseline-vs-patched benchmark evidence, repeated runs, noise-aware verdicts, and repo-seam benchmark commands.
- ▌ Restart Codex Subagents · shakacode bundlePrepare 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.
- ▌ Untrusted Contributor Intake · shakacode bundleSafely 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.
- ▌ Docs · shakacode bundleGenerate, 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.