forgejo-mcp

Convention for building a reproducible demo artifact co-located with each implementation spec, so acceptance has something concrete to read. The author builds the demo against a running instance during the implementation PR; the reviewer reads it during acceptance without re-executing. Triggers on "build demo", "acceptance demo", "showboat", or any spec-linked PR that needs a proof-of-work artifact.

Triage a single issue on Codeberg (or any Forgejo/Gitea-compatible host). Use this skill whenever the user wants to assess, review, or triage a Codeberg issue — including when they paste a codeberg.org issue URL, say "look at issue 42 on owner/repo", "what should we do with this", "review this codeberg issue", or similar. Trigger even when the word "triage" isn't used: any request to read a Codeberg issue and recommend labels, a response, or what to do next falls under this skill. Reads the issue and its comments through the codeberg-mcp connector, then returns an assessment, proposed labels, a proposed English comment, and a two-part verdict (classification + action) for the user to apply manually.

Fetch and display notifications from both GitHub and Codeberg in a unified markdown view with clickable links. Two modes: all (58+ notifications) or next-action (top 5 actionable items). Shows notifications sorted by newest first, grouped by platform. Use /unified-notifications for all notifications. Use next-action mode (python3 .claude/skills/unified-notifications/scripts/fetch_notifications.py next-action) to see only the top 5 items needing your attention. Triggers on requests like "check notifications", "show my notifications", "unified notifications", "next actions", "what needs attention", or "/unified-notifications".