Igapyon Miku Scm
Use only when the user explicitly names `igapyon-miku-scm`, explicitly asks to apply the miku SCM workflow, or explicitly asks to perform Git, GitHub, GitHub Release, or version-management work under miku-soft SCM rules. Do not activate for generic Git or GitHub questions, ordinary repository inspection, or release-note writing.
Install
$ agentstack add skill-igapyon-igapyon-agent-skills-igapyon-miku-scm ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-igapyon-igapyon-agent-skills-igapyon-miku-scm) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
igapyon-miku-scm
Guide source control management for miku-soft projects.
Keep this skill small and add concrete workflows incrementally. Put detailed Git, GitHub, release, and version-management rules under references/ instead of expanding this file.
Current Scope
Support policy guidance and read-only inspection for:
- Git operations
- GitHub operations
- GitHub Releases
- version management
Do not perform remote mutations, history rewrites, tag changes, release publication, or version changes until the relevant workflow is explicitly documented under references/ and the user explicitly requests the operation.
Core Workflow
- Identify the requested SCM area and exact target repository.
- Inspect repository state before proposing or performing work.
- Read [references/scm-rules.md](references/scm-rules.md).
- For local Git status inspection, read [references/local-git-readonly.md](references/local-git-readonly.md).
- For public GitHub source, branch, Issue, or Release inspection, read [references/github-anonymous-readonly.md](references/github-anonymous-readonly.md).
- Preserve unrelated user changes.
- Separate local preparation from remote GitHub operations.
- Report what was inspected, changed, and left pending.
Boundaries
- Treat commit-message composition and other SCM-facing writing, including GitHub PR, Release, and About text, as the responsibility of
igapyon-github-writer. Do not duplicate writing rules in this skill. Use that skill only when it is explicitly requested and within its supported workflow contract. - Use
igapyon-repo-conventionsfor repository layout and repository-side convention work when that skill is explicitly requested. - Keep SCM policy and SCM execution rules in this skill.
Verification
Before finishing, run git status -sb and review any relevant diff. Do not revert unrelated changes.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: igapyon
- Source: igapyon/igapyon-agent-skills
- License: Apache-2.0
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.