Skip to main content
Run any Skill in Manus
with one click
GitHub repository

SeiShinGakuen_ShougiBu

SeiShinGakuen_ShougiBu contains 6 collected skills from hiroshiyui, with repository-level occupation coverage and site-owned skill detail pages.

skills collected
6
Stars
1
updated
2026-05-21
Forks
0
Occupation coverage
2 occupation categories · 100% classified
repository explorer

Skills in this repository

code-review-and-security-audit
information-security-analysts

Review code for quality, correctness, and security vulnerabilities across the GDScript / Rust GDExtension / FFI surface. Use when the user asks to review code, audit for security issues, or check for bugs and anti-patterns.

2026-05-21
commit-and-push
software-developers

Commit code changes and push via Git. Use when the user asks to commit, push, or save their work to the repository.

2026-05-21
docs-engineering
software-developers

Writing/updating project documentation (README, ROADMAP, CLAUDE.md, docs/architecture.md, ADRs, asset-folder READMEs) for SeiShinGakuen_ShougiBu. Use when the user asks to update docs, draft an ADR, write a changelog, or update GitHub Release notes.

2026-05-21
release-engineering
software-developers

Release engineering tasks including version bumping, building signed release APKs, creating git tags, and preparing GitHub Release artefacts. Use when the user asks to prepare a release, bump the version, tag a release, or build for distribution.

2026-05-21
snap-screenshot
software-developers

Capture a screenshot from the connected Android device via adb and save it under docs/screenshots/. Trigger on "snap", "take a screenshot", "screenshot via adb", or any request to capture the device's screen — typical use is grabbing app screens for the README, GitHub Release notes, or bug reports.

2026-04-26
commit-changes-by-topic
software-developers

Split pending working-tree changes into multiple topic-scoped commits. Use when the user has a mix of unrelated edits staged or unstaged and wants them committed as separate, logically coherent commits rather than one big blob. Examples- "commit these by topic", "split this into commits", "break this up into proper commits".

2026-04-22