bernardorubin

@bernardorubin source repo

27 skills
0 followers
4 hours ago last updated

▌
QA · bernardorubin
QA

0 installs
▌
Git Ac · bernardorubin
Use when the user wants to stage all changes and commit locally WITHOUT pushing. Useful when the remote blocks pushes (branch protection, pre-receive hooks, push-blocked config) or when batching commits locally before pushing. Triggers on phrases like "commit but don't push", "stage and commit", "commit locally", "git ac", "add and commit only", "commit without pushing".

0 installs
▌
Shipit · bernardorubin bundle
Use when taking a Jira ticket (or a described feature/bugfix) all the way from investigation through implementation, PR, worklog, and a Slack update — the full ship pipeline. Triggers on "ship ABC-123", "take this ticket end to end", "implement ABC-456 and open a PR", "work this ticket", "shipit", or pasting a Jira URL/key with intent to BUILD and ship (not just read or comment — for plain read/update/ transition use the jira-cli skill instead). This skill orchestrates your existing skills and enforces your hard rules: verify the root cause against real prod data before writing any code, run gh/jira/git commands yourself instead of handing them back, never run deploy/OTA/publish commands, branch with --no-track, and put Jira info in the description (not a comment). Reach for it whenever a ticket needs to go from "assigned" to "review-ready PR + logged + communicated" in one thread. When no ticket key is given, it asks whether to create one first or ship without it.

0 installs
▌
Handoff · bernardorubin
Use when the user wants to hand off the current conversation to a fresh Claude session or another agent — a self-contained handoff document written to the Desktop that a new session reads to pick up exactly where this one left off. Triggers on "handoff", "/handoff", "write a handoff doc", "hand this off to a new session", "pass this to another agent", "context is getting long, write a handoff", "compact this for a new chat to continue". Optional argument describes what the next session will focus on.

0 installs
▌
Standup · bernardorubin
Use when the user wants a daily-standup update drafted from their worklog — "write my standup", "standup update", "what did I do yesterday for standup", "daily standup", "generate my standup from the worklog", "standup notes". Reads the actual worklog (vault-aware, same source /save-session-to-worklog writes) for the last working day's entries, optionally cross-references Jira ticket status, and writes a short standup-notes PDF to the Desktop. The whole point is that it sources from the WORKLOG (ground truth), never from memory or thin notes — so the update reflects what actually got done. For logging today's work INTO the worklog use /save-session-to-worklog; this skill reads it back OUT as a standup.

0 installs
▌
Jira CLI · bernardorubin bundle
Use when the user mentions a Jira ticket, pastes a Jira URL (e.g. https://yourorg.atlassian.net/browse/ABC-123), pastes a ticket key (ACME-1234, WEB-456, ABC-789), or asks to read, update, comment on, transition, assign, link, or search Jira issues. Triggers on phrases like "work on this jira ticket", "update the description in jira", "add a comment to ABC-123", "what's the status of WEB-456", "move this to in progress", "find tickets assigned to me". Wraps the `jira-curl` CLI.

0 installs
▌
QA Video · bernardorubin bundle
Record a QA video of a flow, compress it to a postable size, and attach it to the Jira ticket or PR. Use when a change is behavioral rather than visual and a screenshot cannot show it working — a redirect chain, a state machine, an editor interaction, a timing or async path. Triggers on phrases like "record a video of this", "screen record the QA", "a screenshot won't show this", "attach a video to the ticket", "video QA", "show the flow working".

0 installs
▌
Pr Review · bernardorubin bundle
Use when the user wants code reviewed — a GitHub PR, their local/uncommitted changes, or a whole-repo audit. Confidence-scored review with parallel agents, incremental tracking, and GitHub-comment-ready file output (optionally posted to the PR with --comment). Three modes — (1) PR mode reviews a GitHub PR by number or auto-detected from the current branch. (2) Local mode reviews uncommitted changes plus commits ahead of main when no PR exists. (3) Full-repo mode reviews the entire codebase when the user explicitly asks for a full audit ("audit the whole repo", "review the entire codebase", "full repo audit"). Auto-triggers on phrases like "review this PR", "review my changes", "audit my code", "review my uncommitted work", "audit the whole repo".

0 installs
▌
Create App · bernardorubin bundle
Use when taking a brand-new app from an idea all the way to its first App Store / Play Store / production release — the zero-to-launch pipeline. Triggers on "let's build an app", "new app idea", "start a new project", "take this app to the App Store", "I want to ship this app", "get this app ready for release", or a first-time submission where no version has ever shipped. This is the FIRST-release skill: it owns the one-time gauntlet nobody remembers — production auth instances, custom domain, privacy policy, account deletion, App Privacy answers, DSA trader status, OTA-before-first-submit, and the "nothing was copied from dev" traps that produce silent blank screens. For a later release of an app that has already shipped once, use cut-release instead. For a single ticket on an existing app, use shipit. Holds the hard line: Claude builds to ready and NEVER submits, publishes, or ships an OTA unless the user explicitly says to for that specific action.

0 installs
▌
Vault Init · bernardorubin
Use when the user wants to scaffold a new Karpathy-style LLM Wiki vault for the current project and register it for the vault-keeper skill. Triggers on phrases like "init a vault", "set up a knowledge vault", "create a second brain for this project", "scaffold the wiki", "vault-init", "start a new vault here".

0 installs
▌
Cut Release · bernardorubin
Use when cutting a RELEASE — turning already-merged code into a submittable build. Triggers on "cut a release", "ship a build", "prep the release", "release the app", "build and submit", "cut a build for TestFlight", "new App Store build", "ship version 1.3", "release notes and build". This is the per-RELEASE complement to shipit (which is per-TICKET and stops at a review-ready PR): many shipit runs merge, then one cut-release cuts the version. It pre-flights the release gates (version train / build slot / CI green / version bump), builds the artifact, generates release notes from the merged tickets, and hands back the exact submit command. Enforces the two hard rules that keep releases from failing at upload: verify release preconditions BEFORE building (catches closed version trains and taken build slots), and NEVER run the actual submit / OTA / App Store publish — build to ready, then hand the command back. Not for writing a feature or fixing one ticket (that's shipit); this is for shipping a version made

0 installs
▌
Investigate · bernardorubin bundle
Use when someone asks you to investigate, diagnose, or get to the bottom of something — a production anomaly, a bug report, a "why is X happening", a traffic / payment / email / deploy oddity, a pasted error or alert, or a teammate's question that needs a real answer. Triggers on "investigate X", "can you look into why Y", "figure out what's going on with Z", "dig into this", "someone reported X — find out why", or pasting an incident / alert / error with intent to find the cause (NOT to build a fix — for taking a ticket all the way to a shipped PR use shipit). The common shape is pasting a Slack thread / conversation and saying "investigate this" — read the thread, find the answer, hand back a reply ready to drop into that same thread. This skill enforces the investigation discipline: pull real evidence from the dashboards, logs, and code yourself before drawing any conclusion, make zero assumptions, ask for access or help only when genuinely blocked, and end with a short, evidence-backed Slack update drafte

0 installs
▌
Prd To Jira · bernardorubin bundle
Use when breaking down a PRD, spec, or feature document into Jira tickets. Triggers when user shares a PRD (pasted, Google Doc URL, Jira ticket, file), asks to "create tickets", "break this down", "make Jira tasks", or wants to plan work from a requirements document. Also use when user says "turn this into tickets" or "create an epic for this".

0 installs
▌
Claude Learn · bernardorubin
Use when the user wants to document learnings from the current session into CLAUDE.md files, making future Claude sessions smarter. Triggers on phrases like "document what we learned", "update CLAUDE.md with this learning", "save this to CLAUDE.md", "claude-learn", "review the session for learnings", "what should we document from this session".

0 installs
▌
Review Cycle · bernardorubin
Use when the user wants the full review-AND-FIX cycle on a PR — not just a review, but review → post it to the PR as one living comment → fix the findings worth fixing → run the gates → push → update that same comment, looping until clean. Triggers on "run the review cycle", "review and fix this PR", "do the review loop", "review cycle on PR 512", "review my PR and fix the issues", "review-cycle". Distinct from /pr-review, which only reviews and reports (no fixes, no push): reach for review-cycle when you want the issues actually fixed and pushed, not just listed. It reuses /pr-review as its reviewing engine (including the --comment living-comment machinery) and adds the fix/push/iterate loop on top. Also invoked by /shipit as its self-review step. Uses judgment on which findings are worth fixing.

0 installs
▌
Vault Keeper · bernardorubin
Use when working in a project that has a registered second-brain knowledge vault (Karpathy-style LLM Wiki). Auto-fires when the user documents findings (architecture decisions, integration quirks, debugging discoveries, team facts, ticket epics), looks up domain context (team/integrations/flows/past decisions), ingests raw sources into the wiki, or asks for a vault lint/audit. Resolves the current working directory against `~/.config/claude-pro-skills/vaults.json`; if the project has no registered vault, the skill self-terminates without action. To set up a new vault, use `/vault-init`. Triggers on phrases like "save this to the vault", "what does the wiki say about X", "let's document this finding", "ingest this doc", "lint the wiki", "what's our second brain say about Y".

0 installs
▌
Wrap Session · bernardorubin
Use at end of session when the user wants to do BOTH the worklog write AND the vault sweep in one command — the combined end-of-session wrap-up. Triggers on phrases like "wrap up the session", "wrap session", "save session everywhere", "save to worklog and vault", "worklog and vault", "save both", "do both", "log and save the session", "end-of-session save". For only the worklog use [[save-session-to-worklog]]; for only the wiki use [[save-to-vault]].

0 installs
▌
Save To Vault · bernardorubin
Use when the user wants a deliberate end-of-session sweep that files everything valuable from the WHOLE conversation into the project's knowledge vault (Karpathy-style LLM Wiki) in one pass — not the ambient single-fact writes that [[vault-keeper]] does during normal work. Reviews the entire session, dedupes against what's already filed, and writes each worth-keeping finding into the right wiki page. Resolves the cwd against `~/.config/claude-pro-skills/vaults.json`; if no vault is registered it says so and points to `/vault-init`. Triggers on phrases like "save to vault", "save this session to the vault", "save whatever's valuable from this session", "dump this session to the wiki", "file everything worth keeping", "/save-to-vault".

0 installs
▌
Pr Description · bernardorubin
Use when the user asks to generate, write, draft, or update a pull request description on GitHub. Triggers on phrases like "write a PR description", "draft the PR body", "update the PR description", "fill in the PR", or "generate description for PR <number>". Operates on the current branch's PR by default, or one specified by number/URL. Updates the PR directly via `gh pr edit`, falls back to ~/Desktop/pr-description.md if the GitHub update fails.

0 installs
▌
Session Status · bernardorubin
Use when the user wants a status board of everything worked on in the current session — every feature request, bug fix, question and follow-up they raised, with where each one actually stands and what's blocking or still missing. Triggers on "session status", "where are we", "what's the status of everything", "summarize the work we've done this session", "what did we do and what's left", "what's still open", "what's blocked", "did we ship everything", "loose ends", "recap this session". Built for long multi-ticket sessions where work gets started and quietly never finished. Verifies each item against real state (git, PRs, Jira, gates) instead of trusting the conversation. Read-only — it reports, it never ships, pushes, or fixes anything.

0 installs
▌
Promote To Prod · bernardorubin
Use when the user wants a change taken from a branch all the way to verified production through the staging ladder. Triggers on "promote to prod", "promote this to production", "push it to prod", "get this to prod", "ship it to production", "promote HPY-1234", "staging then prod", "roll this out to prod". Runs the full ladder — PR into staging, wait for checks to go green, merge, verify the change on staging, PR into main, wait for checks, merge, confirm production is healthy AND that the fix is actually live on prod (via Chrome MCP / playwright-cli / curl), capture evidence of the fix working in production, then comment on each Jira ticket and move it to Done or Ready for QA (asking when it isn't obvious; skipped when there is no ticket). Enforces the promotion discipline: never merge on red or pending checks, never open the main PR until staging proved the change didn't break anything, verify the deployed commit before verifying behavior, and if prod comes back broken, revert immediately. NOT for cutting a

0 installs
▌
Git Pull Reapply · bernardorubin
Use when the user wants to safely pull or rebase the current branch from remote while preserving any local work (handles dirty trees, divergent branches via stash + rebase). Triggers on phrases like "pull and reapply", "pull with my changes", "sync this branch safely", "safe pull", "rebase from remote", "pull but keep my work".

0 installs
▌
Claude Modularize · bernardorubin
Use when the user wants to break down a large, monolithic CLAUDE.md file into smaller maintainable pieces distributed across the project directory structure. Triggers on phrases like "modularize CLAUDE.md", "split up CLAUDE.md", "break down our CLAUDE.md", "distribute CLAUDE.md by directory", "claude-modularize", "our CLAUDE.md is too big".

0 installs
▌
Write Slack Message · bernardorubin bundle
Use when the user asks to draft, write, format, or compose a Slack message. Triggers on phrases like "write a slack message", "draft a slack post", "how should I phrase this for slack", "send this on slack", or any request to format text for Slack. Produces a message saved to ~/Desktop/slack-message-for-<recipient>.md ready to copy-paste, with business-casual tone and Slack-compatible formatting.

0 installs
▌
Save Session To Worklog · bernardorubin
Use when the user wants to log today's session work into a monthly worklog file (for standups and invoicing, not git history). Auto-detects project from cwd, vault-aware (routes into the registered vault's raw/work-logs/<user-slug>/ folder when applicable). Triggers on phrases like "save session", "save this session to worklog", "log to worklog", "update my worklog", "add to standup notes", "save-session-to-worklog".

0 installs
▌
Vault Resolve Conflicts · bernardorubin
Use when the user has merge or stash conflicts in a registered vault and wants to auto-resolve by union-merging both sides (keep both incoming and local changes). Vault-only — refuses to run outside registered vaults. Triggers on phrases like "resolve vault conflicts", "union merge the vault", "keep both in vault conflicts", "vault-resolve-conflicts", "fix my vault conflicts".

0 installs
▌
Update Claude Pro Skills · bernardorubin
Use when the user wants to update the claude-pro-skills plugin (this toolkit) to its latest published version. Triggers on "update the claude pro skills", "update my skills to the latest", "update the plugin to latest", "pull the latest claude-pro-skills", "update the toolkit", "update-claude-pro-skills", "get the newest skills". Runs the non-interactive `claude plugin` CLI to update the marketplace from its GitHub source and reinstall the latest version, reports the old → new version, and reminds the user to run /reload-plugins to apply it in the current session. NOT for editing a skill's *content* (that's skill-creator) — this only pulls the newest published build of the plugin.

0 installs

27 published skills