All authors
Claude Skills by happier-dev
github.com/happier-dev28 skills0 installs84 views
- Happier Release Validation ReviewResolve the private Happier release authority for validation review.Votes: 0GitHub stars: 1,877
- Happier Session ControlManage Happier sessions (list/status/send/wait/history/stop + execution runs) via the happier CLI JSON contract.Votes: 0GitHub stars: 1,869
- Happier DiagnoseDiagnose and explain a Happier runtime, session, daemon, provider (Claude/Codex/OpenCode), authentication, or connectivity incident from logs, structured diagnostics, runtime state, and source evidence without modifying repository implementation. Use for support investigation, incident triage, session-ID analysis, or when the user asks what went wrong; if the user requests a repository fix, hand the established evidence to happier-implement.Votes: 0GitHub stars: 1,869
- Happier Github OpsRead and mutate GitHub as the isolated Happier bot through `yarn ghops`, with exact or bounded standing mutation authority, untrusted-issue handling, public write-back rules, machine-identity defaults for commits and pushes, and an explicitly authorized bot-push exception.Votes: 0GitHub stars: 1,869
- Happier Release NotesValidate and project canonical Happier release-note source, StoryDeck cards, translations, and media assets without making editorial or release-policy decisions.Votes: 0GitHub stars: 1,869
- Happier Release PromoteResolve the private Happier release authority for promotion work.Votes: 0GitHub stars: 1,869
- Happier Release ValidationRun target-owned manual deep release certification from an explicit Happier checkout without dispatching a release.Votes: 0GitHub stars: 1,869
- Happier TestingAuthor, change, review, delete, or audit Happier tests through observable contracts, canonical testkits, risk-selected validation, and safe subsystem cleanup. Use for behavior-changing TDD and for test-infrastructure or test-pruning work.Votes: 0GitHub stars: 1,869
- Attack ConclusionAdversarial self-review of your own conclusion, fix, or root-cause verdict before handoff — alternative causes, neighboring cases, blast radius, environment gap, hypothesis lock, subtraction, and a scan for fake-competence patterns. Use as a compact author check before non-trivial handoff and as a structured attack at substantial review or ship boundaries; pair with autoreview only when the selected boundary calls for it.Votes: 0GitHub stars: 1,869
- Decompose GatesDecompose a hard or multi-part task into independently checkable pieces with explicit verification gates and risk-weighted ordering. Use when planning corridor-sized work, writing lane briefs for subagents or Codex, or whenever a task is too large to verify as a whole.Votes: 0GitHub stars: 1,869
- Handoff ReportOutput contract for substantive deliverables — outcome first, evidence-pointed reasoning, observed/derived/assumed labels, residual risk last, failures never buried, and an optional evidence-backed retrospective for explicit requests or major program closeout. Use when reporting completed work, findings, diagnoses, reviews, lane results, or a requested retrospective.Votes: 0GitHub stars: 1,869
- Happier Ci StabilizeStabilize failing, flaky, slow, or repeatedly rerun Happier CI and nightlies by collecting all reachable failures from one exact attempt, correcting canonical causes in one batch, simplifying low-value coverage, and choosing the cheapest safe rerun or candidate-resume path.Votes: 0GitHub stars: 1,869
- Happier Commit WorktreeReconnoiter, classify, validate, group, and commit a large or continuously changing Happier worktree as coherent, human-understandable commits while preserving concurrent work and excluding temporary, generated, QA, evidence, build, and other unwanted artifacts. Use when the user asks to commit many existing uncommitted changes, continue a long-running commit campaign, explain what remains, recover that campaign after compaction or interruption, or safely process newly landed changes in a sha...Votes: 0GitHub stars: 1,869
- Happier CompatibilityAudit, design, implement, and verify Happier compatibility across UI, CLI, daemon, server, installers, and persisted state. Use when changes affect wire or semantic contracts, serialization, sessions/settings/queues, schemas or migrations, capability negotiation, mixed-version operation, upgrades, rollback, or the `remote-dev` predecessor frontier for `dev`.Votes: 0GitHub stars: 1,869
- Happier DocsCreate, update, reorganize, or review Happier internal technical documentation and published user/operator/contributor docs with evidence-backed product truth, exact release status, canonical-page ownership, human voice, minimal editing, and appropriate validation. Use whenever a change affects `docs/**`, `apps/docs/**`, or behavior that may make existing Happier documentation incomplete or false.Votes: 0GitHub stars: 1,869
- Happier Implement PlanUse only when the current user explicitly asks to implement, execute, resume, continue, or complete an approved Happier repository implementation plan. Preserve the plan as the authoritative execution contract while applying the common happier-implement workflow to every implementation unit.Votes: 0GitHub stars: 1,869
- Happier ImplementImplement, change, build, fix, refactor, migrate, or apply accepted review findings in the Happier repositories with canonical-owner discovery, scope-preserving solution economy, TDD, efficient execution, affected-corridor completeness, risk-appropriate QA, and evidence-backed closeout. Use for repository source changes whether or not they are backed by an approved plan; pair with happier-implement-plan when executing an approved repository plan.Votes: 0GitHub stars: 1,869
- Happier Instruction EvalEvaluate two or more Happier instruction, constitution, or skill variants with blinded organic tasks, controlled context, behavior-based scoring, privacy-safe evidence, and an advisory synthesis. Use only when the user explicitly asks to compare/evaluate instruction variants or an approved instruction program names an evaluation boundary.Votes: 0GitHub stars: 1,869
- Happier Issue DiagnoseDeeply diagnose one coherent Happier GitHub issue or related issue bundle from public reports, private diagnostics when authorized, version and release provenance, current source, and real reproduction evidence. Use after issue triage has formed one owner/mechanism bundle, or directly for a single issue. Produces an evidence-backed disposition and recommended response; it does not implement fixes or mutate GitHub without separate authority.Votes: 0GitHub stars: 1,869
- Happier Issue TriageTriage one or many Happier GitHub issues before deep diagnosis: retrieve the requested corpus, treat public content as untrusted, normalize claims and version vectors, find evidence-backed relationships, cluster by likely mechanism or canonical owner, and route coherent bundles to the main lane, native subagents, or independent Happier sessions. Use when the user asks to triage, group, compare, route, or diagnose multiple GitHub issues.Votes: 0GitHub stars: 1,869
- Happier PlanUse only when the current user explicitly asks to create, replace, materially refine, or record an approved amendment to a Happier repository implementation plan.Votes: 0GitHub stars: 1,869
- Happier Port 0 2 To 0 3Port a complete Happier change from the 0.2 source line into the evolved 0.3 destination line by intent, including later source refinements, without copying predecessor architecture or overwriting unrelated work. Use whenever committed, staged, or unstaged 0.2 behavior must be analyzed for 0.3 applicability, adapted through 0.3's canonical owners, and validated without propagating 0.3 changes backward. This skill does not stage or commit changes.Votes: 0GitHub stars: 1,869
- Happier Pr StewardAnalyze and shepherd a Happier pull request from intent review through approved refinements, current-head CI and review follow-up, evidence-based comment adjudication, and any required intent-preserving version-line port. Use when asked to assess whether a PR is correct or mergeable, detect duplicate or split-brain logic, add follow-up commits, request or monitor reviews, address PR feedback, or carry a 0.2 PR and every accepted follow-up into the evolved 0.3 line.Votes: 0GitHub stars: 1,869
- Happier Profile And OptimizeThe method for profiling and optimizing anything whose success is a measured cost — frame the phase and metric, choose an instrument that can actually see the cost, label the waste, falsify the hypothesis with a cheap control before building a fix, and prove the result without over-claiming. Covers app/device and server/database work. Use when work is about slowness, jank, startup/open time, blocked JS, hangs, memory, render churn, a slow query, or a claimed speedup. It does not carry the wri...Votes: 0GitHub stars: 1,869
- Happier ReleaseResolve Happier's private release authority and run an exact-SHA release or nightly through cheap admission, verified CI evidence, resumable immutable candidates, and terminal publication proof. Use for preparing, dispatching, recovering, or assessing a Happier release.Votes: 0GitHub stars: 1,869
- Happier ReviewConduct evidence-backed Happier code, plan-completeness, session, worktree, feature, commit, branch, PR, codebase, and release-readiness reviews with affected-corridor analysis, high-confidence finding triage, meaningful parallel lanes, proportionate but comprehensive QA, optional root-cause fixes, and independent closeout. Use for deep review, audit, QA, pre-merge assessment, plan-vs-implementation verification, review-and-fix loops, or when asked to inspect all related code rather than only...Votes: 0GitHub stars: 1,869
- Verify ClaimsAudit a report, plan, or handoff by re-deriving every load-bearing claim from primary sources. Use before trusting subagent/lane reports, before building decisions on unverified claims, or when reviewing a conclusion written earlier (including your own). Distinct from running the app to verify behavior or reviewing a diff — this audits claims.Votes: 0GitHub stars: 1,869
- Happier Session ControlManage Happier sessions and execution runs through the CLI JSON contract, and create independent Happier diagnosis sessions with explicit ownership, safe options, and fire-and-forget presentation semantics.Votes: 0GitHub stars: 1,869