원클릭으로 Manus에서 모든 스킬 실행

fd-submit-changes

스타4

포크0

업데이트2026년 5월 29일 14:18

Creates a feature branch, stages all changes, commits with a conventional commit message, pushes the branch, and opens a GitHub pull request. Use at the end of every implementation task after all tests pass.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

fluentdata-ai

fluentdata-ai/zil

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

fd-submit-changes

Overview

Use this skill to submit your implementation as a pull request. Follow these steps exactly — do not improvise branch names or commit formats.

Steps

Determine the Jira issue key (e.g. PIP-123) from context.
Create and switch to a feature branch:
```
git checkout -b feat/PIP-123-short-description
```
Branch naming: feat/<KEY>-<3-5-word-slug> (all lowercase, hyphens).
Stage all changes:
```
git add -A
```

Commit with a conventional commit message:

git commit -m "feat(PIP-123): <imperative short description>"

Push the branch:
```
git push origin HEAD
```

Open a pull request using gh pr create:

gh pr create --title "feat(PIP-123): <description>" \
  --body "Closes PIP-123\n\n<summary of changes>" \
  --base dev

Report the PR URL in your final answer.

Notes

Never use --force push.
If gh is not available, report the branch name and ask a human to open the PR manually.
Prefer running validations (tests, linters) before calling this skill. If the environment prevents running them (missing binary, network, etc.), submit anyway and note the skipped validations in the PR body.

이 저장소의 다른 Skills

같은 저장소

get-forecast

fluentdata-ai/zil

Return a concise weather forecast for a given location and (optional) date, including a one-line piece of practical advice. This is the skill the trip-planner agent invokes over A2A.

2026-06-094

fd-explore-repo

fluentdata-ai/zil

Systematic repository exploration procedure. Lists directory trees, reads key files (README, pyproject.toml, package.json, etc.), and produces a structured summary of the codebase layout. Use before planning any implementation task.

2026-05-234

fd-format-code

fluentdata-ai/zil

Runs the project's code formatter and linter (ruff, black, isort, etc.) and reports any remaining issues. Use before committing to ensure code style compliance.

2026-05-234

fd-read-jira-task

fluentdata-ai/zil

Reads a Jira task and all linked issues, returning a structured summary including title, description, acceptance criteria, comments, linked epics, and sub-tasks. Use at the start of every planning session.

2026-05-234

fd-run-tests

fluentdata-ai/zil

Runs the project's test suite and reports pass/fail results. Detects the test framework from the project config and runs the appropriate command. Use after every implementation change before submitting.

2026-05-234

name	fd-submit-changes
description	Creates a feature branch, stages all changes, commits with a conventional commit message, pushes the branch, and opens a GitHub pull request. Use at the end of every implementation task after all tests pass.
license	Apache-2.0

fd-submit-changes

Overview

Use this skill to submit your implementation as a pull request. Follow these steps exactly — do not improvise branch names or commit formats.

Steps

Determine the Jira issue key (e.g. PIP-123) from context.
Create and switch to a feature branch:
```
git checkout -b feat/PIP-123-short-description
```
Branch naming: feat/<KEY>-<3-5-word-slug> (all lowercase, hyphens).
Stage all changes:
```
git add -A
```

Commit with a conventional commit message:

git commit -m "feat(PIP-123): <imperative short description>"

Push the branch:
```
git push origin HEAD
```

Open a pull request using gh pr create:

gh pr create --title "feat(PIP-123): <description>" \
  --body "Closes PIP-123\n\n<summary of changes>" \
  --base dev

Report the PR URL in your final answer.

Notes

Never use --force push.
If gh is not available, report the branch name and ask a human to open the PR manually.
Prefer running validations (tests, linters) before calling this skill. If the environment prevents running them (missing binary, network, etc.), submit anyway and note the skipped validations in the PR body.