Run any Skill in Manus with one click

github-ops

Stars3

Forks0

UpdatedJune 19, 2026 at 06:28

Use this skill when performing GitHub operations for this repo such as creating pull requests, writing commit messages, or managing issues. Covers branch/PR conventions and the commit style used here.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

Geson-anko

Geson-anko/resonite-docker

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	github-ops
description	Use this skill when performing GitHub operations for this repo such as creating pull requests, writing commit messages, or managing issues. Covers branch/PR conventions and the commit style used here.

GitHub Operations

GitHub workflow conventions for this repository.

Commit Messages

Conventional Commits: type(scope): description (feat, fix, docs, refactor, chore).
Imperative mood, subject under ~72 chars. Match the existing history, e.g. fix: give the container audio so Resonite no longer freezes on launch.
Because the value of this repo is in why, prefer commit bodies that explain the failure mode a change fixes, not just what changed.

Pull Requests

Branch from main with a descriptive name: feat/, fix/, docs/, refactor/.
PR title follows Conventional Commits. Keep PRs focused — one logical change.
In the description, state what changed, why, and how it was verified — include the GPU vendor tested on (NVIDIA / AMD / Intel).
Never commit .env (it's gitignored and host-specific).

Issues

Label as bug, enhancement, or documentation. Reference issues in PRs with Closes #123.
For launch-failure bug reports, ask for ./run.sh logs -f output, the GPU vendor, and host distro/desktop session.

More from this repository

same repository

debug-container-launch

Geson-anko/resonite-docker

Use this skill when Resonite fails to launch, crashes on startup, freezes, shows a black/blank window, or has no audio in the container. Maps the common failure modes to their root causes (X11, GPU, shared memory, audio, user namespaces, drive-letter resolution) and the setting that fixes each.

2026-06-193

run-resonite

Geson-anko/resonite-docker

Use this skill when launching Resonite in the container, setting up the host for the first time, or stopping/inspecting the running container. Covers the init.sh → run.sh flow, host prerequisites (X11, GPU, audio, user namespaces), and the named-volume persistence model.

2026-06-193

japanese

Geson-anko/resonite-docker

Use this skill when the user communicates in Japanese or requests Japanese-language output. Ensures natural, technically accurate Japanese for comments, commit messages, and conversation in this repository.

2026-06-193

name	github-ops
description	Use this skill when performing GitHub operations for this repo such as creating pull requests, writing commit messages, or managing issues. Covers branch/PR conventions and the commit style used here.

GitHub Operations

GitHub workflow conventions for this repository.

Commit Messages

Conventional Commits: type(scope): description (feat, fix, docs, refactor, chore).
Imperative mood, subject under ~72 chars. Match the existing history, e.g. fix: give the container audio so Resonite no longer freezes on launch.
Because the value of this repo is in why, prefer commit bodies that explain the failure mode a change fixes, not just what changed.

Pull Requests

Branch from main with a descriptive name: feat/, fix/, docs/, refactor/.
PR title follows Conventional Commits. Keep PRs focused — one logical change.
In the description, state what changed, why, and how it was verified — include the GPU vendor tested on (NVIDIA / AMD / Intel).
Never commit .env (it's gitignored and host-specific).

Issues

Label as bug, enhancement, or documentation. Reference issues in PRs with Closes #123.
For launch-failure bug reports, ask for ./run.sh logs -f output, the GPU vendor, and host distro/desktop session.