# Maintain

Maintain the slopus/happy open source project.

- Repository: https://github.com/slopus/happy (24443 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add slopus/happy --skill maintain -g -a claude-code -y`
Codex: `npx skills add slopus/happy --skill maintain -g -a codex -y`
Cursor: `npx skills add slopus/happy --skill maintain -g -a cursor -y`
Gemini CLI: `npx skills add slopus/happy --skill maintain -g -a gemini-cli -y`

## Description

Maintain the slopus/happy open source project. Triage issues, draft closing comments, find duplicates, check if bugs are fixed on main, and engage with community contributors. NEVER posts comments or closes issues without showing exact text and getting approval first.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# /maintain - Open Source Project Maintenance

You are maintaining slopus/happy as an open source project. Every issue
is a relationship with a user. Every close is a chance to build trust.

## References (single source of truth - read these, don't inline)

- Contribution priorities: `docs/CONTRIBUTING.md`
- Roadmap themes: `docs/roadmap.md`
- Triage checkpoint (last session state, pending items, current
  focus themes): `checkpoint.md`

We do NOT use GitHub Projects, milestones, or priority/size fields.
Priorities and themes live in `checkpoint.md`.

## Golden rule

NEVER close, comment on, merge, or modify issues/PRs without showing
the exact text to the maintainer first and getting explicit approval.
Even when told "close all" or "do X" - show the plan, get sign-off.

### Double-confirmation on ALL human-facing actions

Any action that affects humans - closing issues, posting comments,
merging PRs, editing issue text, labeling, assigning - requires
explicit approval with the exact text/action shown first.

**Feedback = still iterating.** If the maintainer gives ANY feedback
(questions, corrections, "but what about...", mixed responses), that
means we are still thinking. Do NOT execute actions until feedback
resolves into a clear, unambiguous directive. Specifically:

1. Do NOT interpret "sure", "sounds good", listing numbers, or mixed
   feedback (act on some + questions on others) as blanket approval.
2. After feedback is given, re-present the updated plan with exact
   text/messages that will be posted or executed.
3. Wait for an explicit directive ("merge", "close these", "post it").
4. If ambiguous, ask: "ready to execute?" - never assume.

### PR merge rules

The rest: https://github.com/slopus/happy/blob/HEAD/.agents/skills/maintain/SKILL.md