ibrobot-git-flow

スター2

フォーク1

更新日2026年3月23日 08:15

Handles Git commit and push workflow with Euler compliance. Use when user asks to 'git commit', 'git push', '提交代码', '推送代码', 'git status', 'commit -s', 'DCO sign-off', 'check git message', 'euler compliance', '符合规范'. Triggers for 'push to fork', 'commit changes', '提交', '检查提交信息', or when preparing code for submission.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

ソース

openeuler-mirror

openeuler-mirror/IB_Robot

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

IB_Robot Git Workflow Guide

This skill automates code commit process for IB_Robot project (root repo with src directory) and its submodule libs/lerobot. The commit process enforces openEuler Embedded specification.

Core Specifications

1. Commit Message Format

Must strictly follow this structure with exactly one blank line between sections:

<area>: <subject>

<body>

<footer_tags>

Title (: ):
- Format: <module>: <brief description> (e.g., robot_interface: fix moveit crash).
- Length limit: Non-revert commits max 80 chars, revert commits max 102 chars.
- Subject must have at least 2 words, no trailing punctuation.
- Exactly one space after colon.
- No Chinese characters allowed.
Body:
- Must provide detailed description explaining "why" and "what".
- Each line max 100 characters (unless containing URL).
- No Chinese characters allowed.
Footer (Tags):
- Must include Signed-off-by: Name <email>.
- Signed-off-by must be the last line.
- Allowed tags: Fixes, Closes, Co-developed-by, Link.
- Tags must start with capital letter, one space after colon.
- Fixes format: Fixes: <12-char-SHA1>(<original-commit-title>).

2. Mandatory Requirements

All commits must be signed: Use git commit -s to auto-add Signed-off-by to footer. Ensure this line is last.
Remote repositories:
- origin: Personal fork (for pushing code).
- upstream: Main project repo (for submitting Pull Requests).

Execution Steps

Status Determination

If user explicitly requests local commit only (e.g., "commit to local", "only commit no push"), execute only Phase 1, 2, and local commit part of Phase 3. Skip push to remote, PR link, and PR description generation.

Phase 1: Check and Summarize

Run git status in root directory and libs/lerobot separately.
Summarize pending changes to user.

Phase 2: Compose Commit Message

Help user draft commit message (Title, Body, Footer) following specifications above.
Validate: Check title length, format, blank lines, and Chinese characters.

Phase 3: Execute Commit and Push

For submodule libs/lerobot (if changed):

Change to directory -> git add -> git commit -s.
If NOT "local commit only":
- Execute git push origin <branch>.
- Record commit hash.

For root repository:

Return to root directory.
If submodule updated, run git add libs/lerobot.
Run git add . (includes src directory).
Run git commit -s.
If NOT "local commit only":
- Execute git push origin <branch>.
- Get remote info: Extract username and repo name via git remote get-url origin.
- Generate AtomGit PR link: Format https://atomgit.com/<username>/IB_Robot/merge_requests/new?source_branch=<current-branch>.
- Output PR description: Compose detailed PR description from commit message body.

Common Commands Reference

Push to personal fork: git push origin <branch>
Signed commit: git commit -s (opens editor or use -m flag)
Undo last commit (keep changes): git reset --soft HEAD~1

このリポジトリの他の Skills

同じリポジトリ

atomgit-collaboration

openeuler-mirror/IB_Robot

AtomGit 协作路由工具。当用户在 IB_Robot 仓库中提到“PR”、“merge request”、“Issue”、“review”、“comment”、“discussion”、“帮我看看这个 PR”、“看看 #123”、“处理一下评论”、“同步一下 AtomGit 上的协作状态”、“帮我跟进这个合并请求”等泛化协作请求，但没有明确说明是创建、更新、评审、架构审查还是修复评论时调用。此 skill 不直接执行业务动作，而是先识别用户真实意图，再路由到 atomgit-pr、atomgit-issue、atomgit-pr-review、atomgit-pr-architecture-review 或 atomgit-review-resolution。若用户未明确指定 GitHub，则默认优先按 AtomGit 协作处理。

2026-04-152

atomgit-pr-architecture-review

openeuler-mirror/IB_Robot

AtomGit PR 架构评审工具。当用户需要“架构审查PR”、“review architecture compliance”、“检查架构规范”、“审阅PR架构”、“SSOT 合规性检查”、“契约驱动检查”或对指定 PR 做架构维度扫描并提交检视意见时调用。只要目标是本仓库的 PR 架构评审，默认优先使用本 skill，而不是 GitHub 默认 review 能力。

2026-04-152

atomgit-pr-review

openeuler-mirror/IB_Robot

AtomGit PR 评审工具。当用户需要在本仓库或 AtomGit 上“代码审查”、“PR review”、“review pull request”、“审阅PR”、“帮我看看这个PR”、“检查这个PR有没有问题”、“检查Bug”、“logic check”、“获取完整review上下文”、“提交检视意见”或分析指定 PR 的改动与已有评论时使用。只要目标是本仓库的 PR review，默认优先使用本 skill，而不是 GitHub 默认 review 能力。

2026-04-152

intro

openeuler-mirror/IB_Robot

IB-Robot 技能引导入口。当用户输入"介绍"、"有哪些功能"、"有哪些skill"、"我应该用哪个skill"、"help"、"帮助"、"入门"、"intro"、"getting started"、"what skills"、"list skills"、"available commands"、"能做什么"、"怎么用"或首次接触项目时使用。作为所有其他 skill 的统一导航起点，展示分类列表、使用示例并根据仓库当前状态推荐最合适的 skill。

2026-04-152

atomgit-issue

openeuler-mirror/IB_Robot

AtomGit Issue 工作流工具。当用户需要在本仓库或 AtomGit 上“创建Issue”、“查看Issue详情”、“更新Issue”、“关闭/重开Issue”、“create issue”、“fetch issue info”、“update issue”、“report bug”、“feature request”或围绕 Issue 做任何创建/读取/更新动作时调用。只要目标是本仓库的 Issue，默认优先使用本 skill，而不是 GitHub 默认能力。

2026-04-152

atomgit-pr

openeuler-mirror/IB_Robot

AtomGit PR 工作流工具。当用户需要在本仓库或 AtomGit 上“创建PR”、“更新PR描述”、“同步PR标题/正文”、“生成PR摘要”、“create pull request”、“open merge request”、“update PR description”、“generate PR summary”或围绕 PR 管理动作工作时调用。它负责 PR 资源的创建和维护，不负责通用代码 review；只要目标是本仓库的 PR / merge request 管理，默认优先使用本 skill，而不是 GitHub 默认能力。

2026-04-152

name	ibrobot-git-flow
description	Handles Git commit and push workflow with Euler compliance. Use when user asks to 'git commit', 'git push', '提交代码', '推送代码', 'git status', 'commit -s', 'DCO sign-off', 'check git message', 'euler compliance', '符合规范'. Triggers for 'push to fork', 'commit changes', '提交', '检查提交信息', or when preparing code for submission.

IB_Robot Git Workflow Guide

This skill automates code commit process for IB_Robot project (root repo with src directory) and its submodule libs/lerobot. The commit process enforces openEuler Embedded specification.

Core Specifications

1. Commit Message Format

Must strictly follow this structure with exactly one blank line between sections:

<area>: <subject>

<body>

<footer_tags>

Title (: ):
- Format: <module>: <brief description> (e.g., robot_interface: fix moveit crash).
- Length limit: Non-revert commits max 80 chars, revert commits max 102 chars.
- Subject must have at least 2 words, no trailing punctuation.
- Exactly one space after colon.
- No Chinese characters allowed.
Body:
- Must provide detailed description explaining "why" and "what".
- Each line max 100 characters (unless containing URL).
- No Chinese characters allowed.
Footer (Tags):
- Must include Signed-off-by: Name <email>.
- Signed-off-by must be the last line.
- Allowed tags: Fixes, Closes, Co-developed-by, Link.
- Tags must start with capital letter, one space after colon.
- Fixes format: Fixes: <12-char-SHA1>(<original-commit-title>).

2. Mandatory Requirements

All commits must be signed: Use git commit -s to auto-add Signed-off-by to footer. Ensure this line is last.
Remote repositories:
- origin: Personal fork (for pushing code).
- upstream: Main project repo (for submitting Pull Requests).

Execution Steps

Status Determination

Phase 1: Check and Summarize

Run git status in root directory and libs/lerobot separately.
Summarize pending changes to user.

Phase 2: Compose Commit Message

Help user draft commit message (Title, Body, Footer) following specifications above.
Validate: Check title length, format, blank lines, and Chinese characters.

Phase 3: Execute Commit and Push

For submodule libs/lerobot (if changed):

Change to directory -> git add -> git commit -s.
If NOT "local commit only":
- Execute git push origin <branch>.
- Record commit hash.

For root repository:

Return to root directory.
If submodule updated, run git add libs/lerobot.
Run git add . (includes src directory).
Run git commit -s.
If NOT "local commit only":
- Execute git push origin <branch>.
- Get remote info: Extract username and repo name via git remote get-url origin.
- Generate AtomGit PR link: Format https://atomgit.com/<username>/IB_Robot/merge_requests/new?source_branch=<current-branch>.
- Output PR description: Compose detailed PR description from commit message body.

Common Commands Reference

Push to personal fork: git push origin <branch>
Signed commit: git commit -s (opens editor or use -m flag)
Undo last commit (keep changes): git reset --soft HEAD~1