fluid-pr
/fluid-pr
Układa tytuł i opis pull requesta w repo Fluid Framework, pokazuje je do akceptacji i tworzy PR na GitHubie.
- Autor
- microsoft ↗
- Repozytorium
- fluidframework ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 13.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 13.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Układa tytuł i opis pull requesta w repo Fluid Framework, pokazuje je do akceptacji i tworzy PR na GitHubie.
Wyzwalacze z opisu
Oryginalny opis (EN)
Use when creating a pull request in the Fluid Framework repo. Composes a PR title and body following Fluid Framework conventions, proposes them to the user, then pushes the branch and creates the PR on GitHub. Triggers on "create a PR", "make a PR", "open a PR", "submit a PR", or "push and create a PR".
Jak działa
SKILL.md bez nagłówków drugiego poziomu · 71 linii, 570 słów
Podgląd SKILL.md
--- name: fluid-pr description: Use when creating a pull request in the Fluid Framework repo. Composes a PR title and body following Fluid Framework conventions, proposes them to the user, then pushes the branch and creates the PR on GitHub. Triggers on "create a PR", "make a PR", "open a PR", "submit a PR", or "push and create a PR". license: MIT --- <required> *CRITICAL* Do NOT run `gh pr create` until the user has explicitly confirmed via the `ask_user` tool in step 5. Do not skip ahead. *CRITICAL* Add the following steps to your task/todo list using the available Copilot task-management tooling: 1. Confirm you are NOT on `main` or any release branch. If you are, stop and tell the user: you cannot create a PR from a protected branch — they need to create or switch to a feature branch first. 2. Verify that the `origin` remote does not point to `microsoft/FluidFramework`. If it does, stop and tell the user: pushing a branch directly to the main repo is not allowed — they should push to their fork instead. Pipeline changes on branches prefixed with `test/` are an exception. 3. **Load the `fluid-pr-guide` skill NOW** (via the Skill tool) before composing anything. It contains the title conventions, body template, and section guidance you need. Do NOT skip this step or rely on memory. 4. Using the loaded `fluid-pr-guide`, compose the PR title and body following its conventions and template. 5. Print the proposed title and body as text, then immediately use the `ask_user` tool to let the user choose what to do next. Use these exact options: - "Create PR" — Push the branch and open the pull request - "Create draft PR" — Push the branch and open a draft pull request - "Edit" — Revise the title or body before creating - "Cancel" — Don't create a PR 6. If the user picks "Edit", apply their edits and re-present (go back to step 5). If "Create PR" or "Create draft PR", push and create accordingly. If "Cancel", stop. </required> # Pushing and Creating the PR Before pushing, verify that `origin` does not point to `microsoft/FluidFramework`. Run: ```bash git remote get-url origin ``` If the URL contains `microsoft/FluidFramework`, **stop** unless the branch is prefixed with `test/` and the conversation context or changed files indicate that the change needs Azure Pipelines testing. A user request for a "test branch" in that context is sufficient intent to use the exception. Otherwise, tell the user they should push to their fork instead and do not proceed. Once the checks in steps 1–2 pass silently, compose the title and body, print them as text, then use the `ask_user` tool with the four options as described in step 5. This is the only point where the `fluid-pr` flow asks the user a question. ```bash # Push branch (first time) git push -u origin <feature-branch> # Create PR (option 1) gh pr create \ --title "<title>" \ --body "$(cat <<'EOF' <body> EOF )" # Create draft PR (option 2) — add the --draft flag gh pr create \ --draft \ --title "<title>" \ --body "$(cat <<'EOF' <body> EOF )" ``` After creating the PR, output the PR URL so the user can navigate to it. # Updating an existing PR description When asked to update an existing PR's title or body, use `gh pr edit` to apply the changes directly. Specify `--repo <owner/repo>` to avoid ambiguity between forks and upstream. For a description update, write the new body to a temp file, then apply it to the PR: ```bash cat <<'EOF' > "$TMPDIR/pr-body.md" <new body content> EOF gh pr edit <number> --repo <owner/repo> --body-file "$TMPDIR/pr-body.md" ``` To update the title, use `gh pr edit <number> --repo <owner/repo> --title "<new title>"`. After updating, output the PR URL.
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · microsoft/fluidframework | 100 | MIT |
| microsoft/fluidframework | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 40f7f26895c9 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100fluid-pr-guide
Dostarcza styl tytułu, szablon opisu i wskazówki do sekcji przy pisaniu lub przeglądzie pull requestów w Fluid Framework. - 100create-pull-request
Tworzy pull request na GitHubie zgodnie z konwencjami projektu: analizuje commity, zarządza gałęzią i tworzy PR przez gh CLI. - 100create-pr
Otwiera lub aktualizuje pull request na GitHubie dla bieżącej gałęzi, także z wypchnięciem zmian. - 100create-pr
Tworzy pull request: sprawdza gałąź, analizuje zmiany, generuje tytuł i opis oraz wywołuje gh pr create. - 100create-pull-request
Tworzy pull request na GitHubie zgodnie z konwencjami projektu: analizuje commity, zarządza gałęzią, używa szablonu PR i tworzy PR przez gh CLI. - 100create-github-pr
Tworzy pull requesty na GitHubie przez CLI gh i przekazuje kod do przeglądu.