Explore skills
Showing 19471–19500 of 71536 skills
Force-push the current branch to infra-test to trigger a GCP deploy, wait for it to complete, then run each associated DAG pipeline one at a time and wait for each to finish. On full success, updates the PR description with a checklist confirming real GCP infra-test results. Use when the user wants to verify backend changes on the test environment before merging, or run /infra-test.
SatcherInstitute/health-equity-tracker
Stars: 23Claude CodeCodexForce-merge an open PR to main (bypassing review requirements), delete the local branch, pull the updated main, and push it to the personal fork remote. Use when the user wants to close out a PR without waiting for review, or run /merge.
SatcherInstitute/health-equity-tracker
Stars: 23Claude CodeCodexFigure out the best new thing to work on. Pulls open items from the GitHub project board, weighs assignment and labels, then prioritizes cleanly closeable scoped work and issues that would wrap up a milestone. Use when the user wants to know what to work on next, or run /next.
SatcherInstitute/health-equity-tracker
Stars: 23Claude CodeCodexSummarize what's new on dev since the last release and investigate for footguns — config/infra changes, breaking changes, anything that could bring down production. Use before cutting a release, or run /pre-release.
SatcherInstitute/health-equity-tracker
Stars: 23Claude CodeCodexCut a new production release — pre-flight checks, auto-increment tag, publish GitHub release, monitor prod deploy, verify prod loads, targeted Playwright smoke tests, then trigger nightly E2E. Use when the user wants to ship a release or run /release.
SatcherInstitute/health-equity-tracker
Stars: 23Claude CodeCodexGenerate a non-technical executive summary of the previous month's work and post it to the Deliverable Metrics Catch-All Notion page. Pulls GitHub merged PRs across the full repo, Gmail threads, and Google Drive docs for the period; asks interactively about how significant items landed; then translates everything into impact language (health equity, financial sustainability, profile, team velocity) with quantified metrics wherever possible. Use when the user wants to report out on the month's work, catch up the Notion page, or run /report-out.
SatcherInstitute/health-equity-tracker
Stars: 23Claude CodeCodexFlag the open PR as ready for human review — request GitHub review from the two teammates who did not open it, then post a "ready for review" message to the het-core Slack channel with the PR title and link, tagging @channel. Use when the user wants to hand a finished PR off for review, or runs /request.
SatcherInstitute/health-equity-tracker
Stars: 23Claude CodeCodexSenior engineer review of the open PR (or a specified PR number) across four lenses - scientific accuracy, sensitive language, maintainability, and accessibility. Delivers findings inline in the conversation as plain readable prose. Silently writes a GitHub-formatted version to /tmp/het-review.md for optional manual posting. Advances health equity by catching data errors, harmful language, and a11y failures before they reach users.
SatcherInstitute/health-equity-tracker
Stars: 23Claude CodeCodexStart work on a GitHub issue - assign it, move it to In Progress on the project board, branch from clean main, scan for related issues/PRs and sibling codebase patterns to replicate, then begin implementation directly with no confirmation gate. Use when the user says "work on
SatcherInstitute/health-equity-tracker
Stars: 23Claude CodeCodexRefresh the ReadMe contributor recipes (code tabs, line highlights, and prose) after frontend changes land on main. Runs scripts/readme_recipes/sync_recipes.py, then scans recipe prose against the merged diff. Called by /merge after frontend PRs; also usable standalone via /update-recipes [PR number].
SatcherInstitute/health-equity-tracker
Stars: 23Claude CodeCodexA small community registry starter plugin used to verify OpenDesign marketplace install flows.
nexu-io/open-design
Stars: 108kClaude CodeCodexAudit an inherited engagement or implementation against its evidence. Use when taking over work or joining mid-project; distinguish verified facts from inherited claims.
suboss87/FDEOps
Stars: 818Claude CodeCodexDraft a board or executive summary of an engagement using outcomes, risks and investment decisions. Use when the sponsor needs to brief senior leadership.
suboss87/FDEOps
Stars: 818Claude CodeCodexClarify a new customer brief, desired outcome, constraints and evidence gaps. Use for kickoff or a first meeting; do not repeat discovery already supplied.
suboss87/FDEOps
Stars: 818Claude CodeCodexDevelop a business case for an initiative using costs, benefits, risks and evidence. Use when a sponsor needs budget or timeline justification.
suboss87/FDEOps
Stars: 818Claude CodeCodexConfigure or diagnose access to a requested source using available host tools. Use for source MCP setup; source configuration needs no engagement record and credentials stay with the host.
suboss87/FDEOps
Stars: 818Claude CodeCodexReview the portfolio across existing engagement records. Use for status across customers; requires accessible permitted records and does not create missing client histories.
suboss87/FDEOps
Stars: 818Claude CodeCodexTurn meeting notes or a transcript into sourced decisions, changes and next actions. Use after a customer conversation; review consequential record updates before saving.
suboss87/FDEOps
Stars: 818Claude CodeCodexInvestigate a failure, regression or incorrect result in an integration or application, even before it can be reproduced. Use for diagnosis and repair; follow incident authority for live mitigation.
suboss87/FDEOps
Stars: 818Claude CodeCodexPrepare a customer demo or executive walkthrough around an evidenced outcome. Use before show-and-tell to rehearse the journey and prepare a fallback.
suboss87/FDEOps
Stars: 818Claude CodeCodexTrace a customer workflow and identify the problem, baseline and evidence gaps. Use for discovery or an unclear customer brief, before choosing a solution.
suboss87/FDEOps
Stars: 818Claude CodeCodexPlan how to earn customer trust and appropriate access. Use when credibility, permissions or AI policy constrain the engagement.
suboss87/FDEOps
Stars: 818Claude CodeCodexEvaluate an AI workflow against representative cases and its permitted actions. Use for model, retrieval or agent evaluation; tests do not grant release authority.
suboss87/FDEOps
Stars: 818Claude CodeCodexAssess a field lesson for reuse or product feedback without exposing customer context. Use for recurring deployment lessons; distinguish a hypothesis from a validated pattern.
suboss87/FDEOps
Stars: 818Claude CodeCodexTransfer operation of a customer deployment with ownership, evidence and a tested support path. Use for handoff or an engineer rotation, not merely code delivery.
suboss87/FDEOps
Stars: 818Claude CodeCodexFetch requested source material and prepare sourced engagement updates. Use to catch up from external notes or messages; applying updates requires a bound record and confirmation.
suboss87/FDEOps
Stars: 818Claude CodeCodexBuild or change a customer-system integration with explicit data mapping, permissions, retries and reconciliation. Use for connectors, imports, write-back and upstream APIs.
suboss87/FDEOps
Stars: 818Claude CodeCodexCompare feasible approaches to a customer problem and recommend a path with costs, constraints and evidence. Use for an architecture or delivery decision, not implementation.
suboss87/FDEOps
Stars: 818Claude CodeCodexSequence an understood outcome into verifiable delivery slices with dependencies, ownership and acceptance checks. Use for delivery planning, estimation or migration strategy.
suboss87/FDEOps
Stars: 818Claude CodeCodexRun a bounded customer proof of concept to test a consequential uncertainty. Use for a spike or pilot with a question and decision deadline, not a full rollout.
suboss87/FDEOps
Stars: 818Claude CodeCodex