agentleFS
ksip9012ksip9012/agent-skills/github-pr/SKILL.md

github-pr

Skill0 starsChanged 55 days agoMITView on GitHub

作業完了後に PR を作成し、関連 Issue をクローズする。assignees・labels を自動設定する。

  • Commits and pushes

25 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use zeroclaw, github-issue and 2 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • openagenSkill

    zeroclaw

    Help users operate and interact with their ZeroClaw agent instance — through both the CLI (`zeroclaw` commands) and the REST/WebSocket gateway API. Use this skill whenever the user wants to: send messages to ZeroClaw, manage memory or cron jobs, check system status, configure channels or providers, hit the gateway API, troubleshoot their ZeroClaw setup, build from source, or do anything involving the `zeroclaw` binary or its HTTP endpoints. Trigger this even if the user just says things like 'check my agent status', 'schedule a reminder', 'store this in memory', 'list my cron jobs', 'send a message to my bot', 'set up Telegram', 'build zeroclaw', or 'my bot is broken' — these are all ZeroClaw operations.

    Also in 3 projects that use this

  • devstefanchoSkill

    github-issue

    Unified GitHub issue workflow via the gh CLI — fetch an issue (body, labels, comments, image/video attachments) into the session, create a new issue from a template, or update an existing one (body, labels, state, comments). Handles the 404 that plain curl/WebFetch hits on GitHub attachment URLs by downloading with an auth token, and extracts viewable frames from video attachments. Use whenever the user mentions GitHub issues — 이슈 가져와, 이슈 조회, 이슈 등록, 이슈 생성, 이슈 만들어줘, 이슈 업데이트, 이슈 수정, 이슈 코멘트, 이슈 작업, fetch issue N, work on issue N, create an issue, update issue N, file a bug, /github-issue.

    Also in 6 projects that use this

  • SentrySkill

    skill-creator

    Create new agent skills following the Agent Skills specification. Use when asked to "create a skill", "add a new skill", "write a skill", "make a skill", "build a skill", or scaffold a new skill with SKILL.md. Guides through requirements, writing, registration, and verification.

    Also in 8 projects that use this

  • SentrySkill

    commit

    Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.

    Also in 3 projects that use this

The file

Files
SKILL.md

PR 作成スキル

作業が完了したら呼び出す。ブランチ情報と Issue 情報をもとに PR を作成する。

手順

1. ブランチ・Issue 情報の取得

# 現在のブランチ名を取得
git branch --show-current

# ブランチ名から Issue 番号を抽出(例: feat/issue-34-github-pr-skill → 34)
# Issue 情報を取得
gh issue view <番号> --json title,labels

2. リモートへの push 確認

未 push のコミットがあれば push する:

git push -u origin <branch-name>

3. コミット履歴の確認

PR の説明生成に使用する:

git log main..<branch-name> --pretty=format:"%s"
git diff main --name-only

4. PR の作成

~/.dotfiles/github/pull_request_template.md を参考に本文を生成し、以下のコマンドで PR を作成する:

gh pr create \
  --title "<type>: <Issue タイトルを簡潔に>" \
  --base main \
  --assignee "ksip9012" \
  --label "<Issue のラベルと同じ>" \
  --body "$(cat <<'EOF'
## Summary

- <変更内容を箇条書き>

## Related Issue

Closes #<番号>

## Test plan

- [ ] <確認事項>

🤖 Generated with [Claude Code](https://claude.com/claude-code)
EOF
)"

5. 完了報告

作成した PR の URL をユーザーに伝える。

注意事項

  • --assignee は常に ksip9012 を設定する
  • --label は Issue に設定されているラベルと同じものを使う。ラベルがリポジトリに存在しない場合は先に作成する:
    gh label create "<ラベル名>" --color "<カラーコード>"
  • PR タイトルは <type>: <説明> の形式にする(例: feat: github-pr スキルを追加する)
  • Closes #<番号> を本文に含めることで、PR マージ時に Issue が自動クローズされる
  • レビュー依頼(--reviewer)は設定しない

Gotchas

(まだ記録なし。実際に失敗したパターンに遭遇したら、ここに追記していく)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.