igapyon-miku-scm

Files (113)

• SKILL.md
• openai.yaml · agents/
• 2026-10-23-issue-approval-implementation-plan.md · docs/
• prompt-runner-ai-involvement-reduction-pattern.md · docs/
• work-cycle-lifecycle-redesign.md · docs/
• approval-handoff.md · references/
• deterministic-workflow-runner.md · references/
• github-about-writing.md · references/
• github-anonymous-readonly.md · references/
• github-backup-branch.md · references/
• github-branch-status.md · references/
• github-cli-static-helper-policy.md · references/
• github-issue-close.md · references/
• github-issue-comment.md · references/
• github-issue-create.md · references/
• github-issue-label-update.md · references/
• github-issue-rewrite-handoff.md · references/
• github-issue-update.md · references/
• github-post-push-pr-url.md · references/
• github-post-recommit-publish.md · references/
• github-pr-recommit-push.md · references/
• github-pr-soft-reset-recommit.md · references/
• github-pr-writing.md · references/
• github-readonly-cache.md · references/
• github-release-tag-handoff.md · references/
• github-release-writing.md · references/
• github-repository-url.md · references/
• github-writing-rules.md · references/
• local-git-readonly.md · references/
• local-git-snapshot.md · references/
• performance-benchmark.md · references/
• repository-maintenance.md · references/
• repository-precommit-checks.md · references/
• runtime-and-test-suites.md · references/
• safety-cost-and-errors.md · references/
• scm-rules.md · references/
• version-increment-confirmation.md · references/
• version-increment.md · references/
• version-tag-release-audit.md · references/
• version-workflow-runner.md · references/
• work-commit.md · references/
• workflow-contracts.md · references/
• workflow-routing.md · references/
• writing-mode.md · references/
• github-issue-close.mjs · scripts/
• github-issue-comment.mjs · scripts/
• github-issue-create.mjs · scripts/
• github-issue-label-update.mjs · scripts/
• github-issue-read.mjs · scripts/
• github-issue-update.mjs · scripts/
• github-issues-cache.mjs · scripts/
• miku-scm-benchmark.mjs · scripts/
• miku-scm-cli-contracts.mjs · scripts/
• miku-scm-command-runner.mjs · scripts/
• miku-scm-error-report.mjs · scripts/
• miku-scm-fixed-command-runner.mjs · scripts/
• miku-scm-github-readonly.mjs · scripts/
• miku-scm-handoff.mjs · scripts/
• miku-scm-help.mjs · scripts/
• miku-scm-human-output.mjs · scripts/
• …and 53 more

SKILL.md (first lines)

# igapyon-miku-scm

Run documented miku-soft source-control workflows with a small runtime context.
Detailed policy remains under `references/` for design, maintenance, legacy
operations, and exceptions; migrated workflows execute through the fixed runner.

## Current Scope

Support repository status and maintenance; PR-text, Release, About, and Issue work;
recommit, publication, backup, and post-merge work; version and release audits;
and deterministic READONLY, preflight, and apply workflows.
Also support explicit `miku-scm sync pull` and `miku-scm sync push` requests.

Here, GitHub includes GitHub Enterprise and similar hosting services. Do not
restrict execution to `github.com`. Derive the host from the selected remote
for local workflows; for Issue workflows use `[host/]owner/repo`, retaining the
host when it is known. Fixed helpers use that host for URL checks and compatible
GitHub CLI/API calls. An unavailable command or incompatible API is reported at
that operation, rather than rejecting a service by hostname.

Potentially sensitive filenames stop an ordinary commit before staging. Show
the returned paths and wait for explicit user consent. After consent, rerun
the same requested stage with `--allow-sensitive-path <path>` for each agreed
path; pass these options to `work.commit` or `repository.sync.push.prepare`.
Do not infer this consent from the original commit/push request or reuse it
for additional paths. This local consent does not authorize an Issue write.

Draft locations and names are conventions: warn and import a working copy when
they differ, retaining the source. An already satisfied operation returns
`up-to-date` without a mutation or a new approval handoff. Missing operational
ignore setup is reported and handled through Git's local `info/exclude`, so it
does not stop the requested workflow or edit tracked `.gitignore` files.

Platform names and line-ending conventions are advisory. On Linux or other
platforms, report a notice and attempt the same fixed commands; their actual
outcome determines success. Read CRLF/CR drafts with a notice and normalize
submitted text to LF while retaining the source bytes and their review digest.

## Activation-Only Fast Path

If no concrete SCM task is given, acknowledge activation and ask what is wanted.
Do not inspect the repository or load detailed references yet.

## Normal Work Flow

The usual sequence is:

1. `miku-scm git add commit`: run `work.commit --apply` to stage and commit
   the current changes.
2. `miku-scm draft recommit push`: compose and save the Pull Request title
   and body as a text file, use that draft for the recommit, push the work
   branch through `pr.recommit.push`, and rename the local branch with
   `-done`.
3. The human creates and merges the Pull Request on GitHub using the saved
   draft.
4. `miku-scm github merge done`: the human reports that the Pull Request was
   merged. Run `repository.post-merge.next-work --confirmed-merged --apply`
   to refresh the base, check the recommended tag, and create and switch to
   the next work branch, following Git's tracking settings for the shared base.

Run each SCM stage when the user requests it, with that workflow's checks and
authorization. In this Skill, `draft` means saving PR text; GitHub PR creation
and merge are the human's step. The older `pr recommit push` spelling remains
a compatible alias for `draft recommit push`.

The `miku-scm draft recommit push` workflow and its `miku-scm pr recommit push`
alias are owned exclusively by this Skill. Do not activate or run
`igapyon-github-writer` for their PR-drafting or soft-reset portions.

### Sync Instructions

In user requests, `miku-scm` names this Skill; `sync pull`, `sync push` and
`github merge done` are instructions passed to it, not standalone shell commands.
The Skill invokes the documented Node.js runner and its CLI arguments below.

The combined cycle is `sync pull` → edit work and explicitly increment the
version when needed → `sync push` → human PR creation/merge → `sync pull`.
Both commands use Node.js, Git, and local operational files under
`workplace/miku-scm/sync/`. The helper configures local exclusion with a notice
when necessary. The default remote is
`origin`; the helper resolves the shared base or stops for an explicit
`--base`. See the references for setup and base selection.

`miku-scm sync pull` runs `repository.sync.pull --repo <target-repo> --apply`.
It fetches the shared base and chooses no-op, fast-forward, or rebase of
unpublished commits with a recorded branch base. Unsafe replay or integration
conflicts stop with recovery information. Staged/unstaged/untracked work is
retained, using a backup and exact retained stash when integration needs them.
Only on a local `-done` branch does the fixed helper verify the exact GitHub
PR as merged and contained in the fetched base before creating the next work
branch using Git's tracking settings for the shared base and carrying work
over. Unmerged or mismatched PR evidence stops that transition. Ordinary branches do not query
PR merge state. Pull requires Git 2.45 or newer. Its `-done` check uses GitHub
CLI when installed; if `gh` is missing, the fixed helper reads the selected
host's PR API anonymously over HTTPS. If PR reads are unavailable, the helper
returns `confirmation_required: true` before changing work. Show its repository,
published branch, HEAD, base and merge question, then wait for the user's reply.
After a clear affirmative merge report for that displayed target, continue with
`repository.sync.pull --repo <same-repo> --confirm-merged <returned-operation-id>
--apply`. Carry the ID from this conversation; do not select a global pending
operation or infer confirmation from the original sync request. A reply such as
`はい、マージ済みです` or `github merge done` answering this question confirms
that pending sync; use its continuation so staged work is retained. Standalone
`github merge done` retains its existing meaning. A negative or ambiguous reply
does not authorize continuation. The helper checks that the saved work and
remote are unchanged, refetches the base and records human confirmation distinctly
from API verification. Unmerged, mismatched, malformed or incomplete PR evidence
does not offer this confirmation path. See the sync reference for cancellation.
Fetch respects the remote's fetch and tag settings;
incomplete branch coverage stops divergent replay instead of fetching
excluded branches.
Successful next-work output explicitly names the `New work branch`; other
pull results show the `Current branch` without implying a new branch was created.
It never pushes. See [sync-pull.md](references/sync-pull.md) for recovery.

`miku-scm sync push` stages and commits all ordinary non-ignored pending work
when dirty, then drafts PR text, backs up and collapses the branch's commits
into one PR-text commit, pushes the work branch, and renames the local branch
with `-done`. Clean work skips the ordinary commit; no commits above the base

From igapyon/igapyon-agent-skills, Apache-2.0.

More from igapyon/igapyon-agent-skills