跳到正文
cccskills
免费在 GitHub 公开

publish-branch

Push current branch to remote origin and generate PR title and description from branch name and commit history. Use when publishing a branch, creating a PR, pushing to remote, or preparing PR content. Triggers on publish branch, push branch, create PR, open pull request, push and PR.

中文简介正在准备中。当前显示原文说明。

集成工具JiraGitHub
查看安装方法

包含的文件(2)

  • SKILL.md3.6 KB
  • assets/.gitkeep0 B

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Publish Branch

You are a branch publishing agent that pushes the current branch to the remote, analyzes commit history, and generates a properly formatted PR title and description ready for submission.

When to Use

  • "Push this branch and create a PR"
  • "Publish my branch"
  • "Generate PR content"
  • When a feature branch is ready for review
  • After CI passes and code is ready to submit

Not for:

  • Just committing changes (use conventional-commit)
  • Monitoring CI after push (use ci-watcher)
  • Reviewing existing PRs (use GitHub CLI directly)

Context

Aquarium component library:

  • Language: TypeScript (React + Ant Design + Storybook)
  • Branch Naming: <type>/<description>-<TICKET> (e.g., feat/add-tooltip-MPD-59)
  • PR Size: < 400 lines preferred
  • Jira Instance: rokt.atlassian.net

The Process

Step 1: Verify Clean State

Check for uncommitted changes:

git status

If there are uncommitted changes, invoke the conventional-commit agent first.

Step 2: Push to Origin

git push -u origin $(git rev-parse --abbrev-ref HEAD)

Step 3: Gather Repository Information

git remote get-url origin
git rev-parse --abbrev-ref HEAD

Parse the remote URL to extract org and repo name (handles SSH and HTTPS).

Step 4: Analyze Changes

Review commit history since branching from main:

git --no-pager log main..$(git rev-parse --abbrev-ref HEAD)

Use git --no-pager diff main...HEAD for deeper analysis if needed.

Step 5: Generate PR Title

Parse the branch name following this convention:

Branch Format: <type>/<description>-<TICKET>

Title Format: <type>: description

Rules:

  • Use conventional commit format for the title
  • NO scopes in parentheses — CI rejects feat(scope):, only feat: is valid
  • Generate concise description from commits and changes (not the branch name verbatim)
  • Keep title under 80 characters

Examples:

  • feat/add-tooltip-MPD-59
    • feat: add help icon tooltip pattern with RoktHelpCircle
  • fix/button-hover-state-MPD-100
    • fix: correct hover state color on disabled buttons

Step 6: Generate PR Description

Use this template:

## Summary

[High-level overview of changes and context for reviewers]

## Jira Ticket

[TICKET_ID](https://rokt.atlassian.net/browse/TICKET_ID)

## Test Plan

[Testing approach and verification steps]

- [ ] Tested locally
- [ ] Unit tests pass
- [ ] Integration tests pass (if applicable)

Step 7: Create PR

gh pr create --title "<title>" --body "$(cat <<'EOF'
<description>
EOF
)"

Constraints

  • DO generate PR title from branch name AND commit content (not branch name alone)
  • DO include Jira ticket link in the PR description
  • DO ask if the user tested locally before marking the checkbox
  • DO keep title under 80 characters
  • DO NOT push to main/master directly
  • DO NOT include test-only changes in the PR title/summary
  • DO NOT create the PR without showing the user the title and description first

Output Format

  1. Push confirmation with branch name and remote
  2. PR title in a code block
  3. PR description in a markdown code block
  4. PR link after creation (or pre-filled compare URL if manual creation preferred)

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Monitor CI/CD checks until green or failure with auto-diagnosis, failure classification (related vs flaky vs external), self-healing fix attempts, and smart retriggers for flaky E2E tests. Use for CI monitoring, pipeline failed, build broken, flaky test, CI red, check status, watch pipeline, Buildkite, GitHub Actions, re-trigger CI.

中文简介正在准备中。当前显示原文说明。

mParticle/aquarium82026年10月14日 更新

Composite workflow that stages all changes, creates a conventional commit, pushes to origin, and monitors CI until green or failure. Use when you want to commit and push in one step with CI monitoring. Triggers on commit and push, push and watch, commit push watch, ship it, push and monitor CI.

中文简介正在准备中。当前显示原文说明。

mParticle/aquarium82026年10月14日 更新

Analyze staged git changes and generate a conventional commit message with proper type, scope, and description. Use when committing code changes, creating commits, writing commit messages, or staging files for commit. Triggers on commit, commit changes, stage and commit, conventional commit, commit message.

中文简介正在准备中。当前显示原文说明。

mParticle/aquarium82026年10月14日 更新

Detects deeply nested loops with duplicated inline logic and recommends extracting into small, named functions. Enforces DRY principles, single-responsibility helpers, and flat iteration patterns. Triggers on nested loop, duplicated logic, extract function, DRY, refactor loop, code review, deeply nested, inline logic, readability.

中文简介正在准备中。当前显示原文说明。

mParticle/aquarium82026年10月14日 更新

Analyze the current repo structure, build system, test setup, and conventions to provide a practical onboarding guide. Use when new to a codebase, joining a project, or wanting to understand how a repo is organized. Triggers on getting started, new to repo, onboard, how does this repo work, repo structure, codebase overview.

中文简介正在准备中。当前显示原文说明。

mParticle/aquarium82026年10月14日 更新

End-to-end Jira ticket implementation — fetches ticket, creates branch, implements changes, builds, commits, pushes, and creates a PR. Designed for non-engineers to ship design system changes by just providing a ticket ID. Triggers on implement ticket, ship ticket, do ticket, build ticket, implement MPD.

中文简介正在准备中。当前显示原文说明。

mParticle/aquarium82026年10月14日 更新

查看 mParticle 的全部技能

报告此技能的问题