agentsclimarketplace

Igapyon github writer

Skill igapyon/igapyon-agent-skills/skills/igapyon-github-writer

A personal repository for managing Agent Skills used for Japanese Note/Qiita article writing, companion-style technical and music post writing, GitHub text drafting, and Mikuku character-agent workflows.

Install
npx -y skills add igapyon/igapyon-agent-skills --skill igapyon-github-writer

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use only when the user explicitly asks to draft GitHub PR text, GitHub Release notes, GitHub About text, rebuild local commits with soft reset and a drafted PR text as the commit message, create a local backup branch, or inspect the current branch status using igapyon-github-writer. If the user only asks whether such a skill exists, mention this skill as an available option but do not apply it until asked.

SKILL.md

6.0 KB, as published. Nobody here has run it

igapyon-github-writer

This skill drafts Markdown text for GitHub surfaces from local repository evidence. It can also save drafted GitHub text to a local Markdown file, rebuild local commits with soft reset and a drafted PR text as the commit message, create a local backup branch at the current HEAD, and report the current branch status as preparation for GitHub writing work.

Use it only for GitHub writing text, local draft-file saving for that text, explicit PR soft-reset recommit work, explicit local backup-branch creation, and the local branch-status checks that prepare that writing. Do not create PRs, tags, releases, issues, non-backup branches, commits, or remote changes unless the user separately asks for that operation.

Do not use this skill for generic commit summaries, changelogs, branch inspection, backup operations, or repository cleanup unless the user explicitly asks for GitHub PR, GitHub Release, GitHub About text, PR soft-reset recommit from drafted PR text, local backup-branch creation through this skill, branch status through this skill, or names this skill.

If the user asks whether there is a skill for GitHub PR, Release, or About text, mention this skill as an available option, but do not apply it until the user asks to use it.

Mode Phrases

After this skill is active, choose the workflow mode from the user's wording. The wording does not need to exactly say pr text or release text; similar phrases are enough.

Examples:

  • PR mode: pr textつくりたい, PR文面を作りたい, pull request本文, プルリク説明, PRタイトルと本文
  • Release mode: release textつくりたい, リリース文を作りたい, release notes, リリースノート, GitHub Release本文
  • About mode: GitHub Aboutを書きたい, About文, リポジトリ説明, GitHub説明文
  • PR Soft Reset Recommit mode: PR文面でsoft resetしてcommitし直す, PR文面をcommit messageに反映して再コミット, 作文したPR文面でgit commitし直す
  • Backup Branch mode: github-writerでバックアップブランチ, backup/2026-06-27-2230 みたいなブランチを作る, 現在HEADをバックアップ, soft reset前のバックアップだけ作る
  • Branch Status mode: github-writerでブランチ状況, 今のブランチの状況, PR前にブランチ状態を見たい, 現在ブランチの確認

If the mode is clear but required evidence is missing, do not draft yet. Ask for the missing target, except for PR mode's default target rule:

  • PR mode: if the user asks for PR text without specifying a commit ID, Git range, branch comparison, or working-tree target, first run git log --oneline --decorate -1 to resolve the current latest commit, then use that single commit as the PR target. Do not include uncommitted working-tree changes.
  • Release mode: ask for the start commit ID, explicit Git range, or tag/range target.
  • About mode: ask whether to use README.md and project metadata, or ask for the source text when repository evidence is not obvious.

Core Workflow

  1. Identify whether the request is for PR, Release, About text, PR Soft Reset Recommit, Backup Branch, or Branch Status.
  2. Read references/github-writing-rules.md before drafting.
  3. Read the mode-specific reference: references/pr-writing.md, references/release-writing.md, references/about-writing.md, references/pr-soft-reset-recommit.md, references/backup-branch.md, or references/branch-status.md.
  4. Inspect only the repository evidence needed for the requested mode.
  5. Draft or report from evidence without inventing unsupported facts.
  6. For PR, Release, and About modes, save the drafted Markdown using the shared draft-save rules unless the user says not to save.
  7. Return the final answer using the format required by the selected reference.

Reference Use

Use references/github-writing-rules.md for shared evidence collection and hallucination-prevention rules.

Use these mode-specific references:

Use index.json as the discovery index when you need to confirm the available bundled reference files, but treat SKILL.md and files under references/ as the source of truth.

Keep this SKILL.md lean. Put detailed commands, output shapes, and mode-specific rules under references/.

Verification

Before finishing:

  • ensure the final answer contains no absolute paths, home directories, or working directories
  • ensure unsupported items are marked 未確認, 要確認, or omitted
  • for PR, Release, and About modes, ensure the drafted Markdown is wrapped with ~~~~markdown and ~~~~; if a file was saved, mention only the relative saved path outside the wrapped block

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.