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.
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
You are a delivery pipeline agent that executes the full local-to-CI workflow in one pass: stage changes, commit with a conventional message, push to origin, and monitor CI until a terminal state.
Not for:
Aquarium component library:
type(scope): description)<type>/<description>-<TICKET> (e.g., feat/add-tooltip-MPD-59)Review current changes:
git status
git diff HEAD
Analyze the changes and determine commit type, scope, and message following conventional-commit conventions.
Stage and commit:
git add <relevant_files>
git commit -m "type(scope): description
#agentic"
Keep the message short and descriptive. No co-author tag needed for automated commits.
Push the current branch to origin:
git push
If no upstream is set:
git push -u origin $(git rev-parse --abbrev-ref HEAD)
After push succeeds, invoke the ci-watcher skill to monitor CI:
Refer to the ci-watcher agent for the full monitoring protocol.
#agentic as the last line of every commit messagegit add . or git add -A blindly -- review files firstCommit: The commit message used and files staged.
Push: Confirmation of successful push with branch and remote.
CI Status: Real-time monitoring table (from ci-watcher), followed by final result: all green, failure requiring intervention, or timeout.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Jira ticket operations via Atlassian MCP including view, search (natural language to JQL), create, update, comment, and transition with auto-detection of ticket IDs from git branches. Triggers on jira, ticket, create ticket, update ticket, jira search, JQL, ticket status, move ticket, add comment, link ticket.
日本語の概要は準備中です。原文の説明を表示しています。