🔍
DevOpsTypeScript

Happier Runtime Diagnosis

by happier-dev

Happier Runtime Diagnosis is a DevOps skill for Claude Code, published by happier-dev in happier.

1.5K stars131 forkson happier-dev/happierAdded 2026/08/19+1% in starsRepository updated 2026/08/19
ai-agentsclaudeclaude-codecodexgeminikimiopencodeqwenvibe-codingvibecoding
Install in seconds
Install Happier Runtime Diagnosis
Copy Happier Runtime Diagnosis into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.
terminal
npx degit https://github.com/happier-dev/happier/tree/dev/skills/happier-diagnose ~/.claude/skills/happier-diagnose

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/happier-dev/happier.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file
skills/happier-diagnose/SKILL.md in happier-dev/happier
Installs to
~/.claude/skills/happier-diagnose
Collection
One of 24 skills cataloged from this repository
Category
DevOps798 skills

What Happier Runtime Diagnosis does

Happier Runtime Diagnosis investigates Happier runtime, session, daemon, provider, authentication, and connectivity incidents from logs, diagnostics, runtime state, and source evidence without modifying repository implementation. Use for support investigation or incident triage.

Happier Runtime Diagnosis is cataloged under DevOps on DirSkills. Happier Runtime Diagnosis comes from a repository tagged ai-agents, claude, claude-code, codex and gemini.

Documentation

README

Happier Diagnose

Investigate a Happier runtime/support incident from primary evidence, determine the originating cause when the evidence supports it, and report what is known, what is derived, and what remains unverified. Diagnosis is read-only: do not edit repository source or silently turn the investigation into a fix.

For a GitHub issue or coherent issue bundle, use skills/happier-issue-diagnose; it owns untrusted issue intake, private maintainer-evidence capability checks, version/release disposition, and the GitHub-facing report while composing this runtime evidence method when applicable. For a raw multi-issue corpus, use skills/happier-issue-triage first.

This is the opening of the README. Read the full README on GitHub.

Commands Happier Runtime Diagnosis provides

Slash commands named in this skill’s SKILL.md, listed in the order they first appear.

  • /happier-diagnose

Frequently asked about Happier Runtime Diagnosis

  • What else does happier-dev publish alongside Happier Runtime Diagnosis?

    Happier Runtime Diagnosis is one of 24 skills that DirSkills catalogs from happier-dev/happier, the repository it ships in. Its siblings there include Attack Your Conclusion, Decompose With Gates and Handoff Report. Each one is a separate skill with its own page in this directory, installs the same way Happier Runtime Diagnosis does, and is maintained by happier-dev in that same repository. The rest of the collection is listed on the happier-dev/happier page.

  • How does Happier Runtime Diagnosis compare to other DevOps skills?

    Happier Runtime Diagnosis ranks #337 by stars among the 798 DevOps skills in this catalog. The most-starred ones next to it are Backend Patterns, API Connector Builder and Migration. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Happier Runtime Diagnosis against them. Open each page to compare what they document and how they install.

More from happier-dev/happier

Happier Runtime Diagnosis is one of 24 skills cataloged on DirSkills from happier-dev/happier.

See all 24 skills
🛡️
2w ago

Attack Your Conclusion

Attack Your Conclusion is an adversarial self-review checklist for testing your own fix, root-cause verdict, or conclusion before handoff. It systematically probes alternative causes, neighboring cases, blast radius, environment gaps, hypothesis lock, and fake-competence patterns.
Quality
1.5K131
🧩
2w ago

Decompose With Gates

Decompose With Gates splits hard or multi-part work into independently checkable pieces with explicit verification gates and risk-weighted ordering. Use it when planning corridor-sized tasks, writing lane briefs for subagents, or whenever a task is too large to verify as a whole.
AI Engineering
1.5K131
📋
2w ago

Handoff Report

Handoff Report structures substantive deliverables with outcome first, evidence-pointed reasoning, observed/derived/assumed labels, and residual risk last. Use it when reporting completed work, findings, diagnoses, reviews, lane results, or a requested retrospective.
Writing
1.5K131
🗂️
2w ago

Happier Commit Worktree

Happier Commit Worktree turns a large or changing worktree into coherent, reviewable commits by classifying, validating, and grouping paths while excluding artifacts and preserving concurrent work. Use it when you need to commit many existing changes or continue a long-running commit campaign.
Automation
1.5K131
🧩
2w ago

Happier Compatibility

Happier Compatibility audits wire, semantic, persistence, and installer contracts so changes can safely introduce upgrades, rollback, mixed-version operation, and migrations without breaking released behavior.
Quality
1.5K131
📝
2w ago

Happier Documentation

Happier Documentation creates, updates, and reviews internal technical docs and published user/operator/contributor documentation with evidence-backed product truth and release-status accuracy. Use it when changes affect docs or behavior that may make existing documentation incomplete or false.
Writing
1.5K131