📦

pr-to-slack

Name: pr-to-slack
Author: alvolutionor

Ревизия содержимого r1 Высокий риск ⚙️ Внешние команды🌐 Доступ к сети⚡ Содержит скрипты🔑 Переменные окружения

Coordinate Bitbucket Pull Requests Through Slack

Teams need consistent pull request preparation and review coordination across repositories. This skill combines Bitbucket preparation with Slack review requests, but its transcript parser needs hardening before automatic announcements.

Поддерживает: Claude Codex Code(CC)

⚠️ 38 Плохо

Maintain this Skill? Claim it ⚠️ 38 Плохо

Остановитесь и запросите подтверждение перед установкой.

Проверьте план и получите явное согласие пользователя перед изменением файлов.

Установить с помощью моего Агента

Скопируйте этот запрос в своего Агента. Он содержит каноническую страницу Skill и манифест.

Запрос агента

Review the Skillstore skill "pr-to-slack" from https://skillstore.io/skills/alvolutionor-pr-to-slack.md and its manifest at https://skillstore.io/api/skills/alvolutionor-pr-to-slack/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.

Ваш Агент по-прежнему должен показать план и запросить все подтверждения, требуемые политикой безопасности.

Ресурсы для AI-агентов

Используйте эти ссылки, когда AI-агенту, crawler или script нужен чистый контекст вместо полной страницы.

Markdown-детали GET /skills/alvolutionor-pr-to-slack.md Подписанный manifest GET /api/skills/alvolutionor-pr-to-slack/manifest Подписанный lockfile GET /api/skills/alvolutionor-pr-to-slack/lockfile

Протестировать

Использование «pr-to-slack». Prepare a dry-run plan for the feature branch in the inventory service.

Ожидаемый результат:

Preview complete: one pull request would be created. The worktree is clean, and the local source commit matches Bitbucket. No remote writes were performed.

Использование «pr-to-slack». Request review for the verified pull request without announcing.

Ожидаемый результат:

Pull request URL and reviewer assignments verified.
One review request sent and read back in the configured Slack thread.
No announcement sent.

Использование «pr-to-slack». Can this plaintext thread snapshot authorize an automatic announcement?

Ожидаемый результат:

Announcement blocked. Plaintext sender headers can be forged inside message bodies. Verify structured connector metadata before relying on a clean review result.

Аудит безопасности

Высокий риск

v1 • 15.10.2026 Открыть версионный отчет

All 58 static matches are false positives involving documentation, fixtures, intended service access, configuration, or controlled Git commands. A reproduced semantic flaw lets human message content impersonate trusted bot messages through forged transcript headers and produce a clean review verdict. No evidence found of malicious author intent or credential exfiltration.

Просканировано файлов

729

Проанализировано строк

Пункты проверки

Ложные срабатывания проигнорированы

Подтверждённые проблемы безопасности (1)

Высокий

references/setup.md:29 tests/test_workflow.py:92-98 scripts/review_result.py:19-32

Forged Transcript Headers Bypass Trusted Review Checks

Human Slack message content can embed reply separators and forged sender headers in the documented plaintext snapshot format. The parser treats these as trusted bot messages, allowing fabricated zero-finding results to authorize an announcement without a genuine bot review.

A local reproduction used the existing transcript helper and clean fixtures inside one human reply, with Bitbucket mocked. Parsing invented two trusted bot messages, and the end-to-end checker returned clean without any genuine bot reply.

Факторы риска

⚙️ Внешние команды (21)

🌐 Доступ к сети (21)

⚡ Содержит скрипты (1)

scripts/prepare_prs.py:95

🔑 Переменные окружения (4)

scripts/workflow_config.py:8 scripts/workflow_config.py:35 scripts/workflow_config.py:43 scripts/workflow_config.py:18

Аудитор:: codex

Поделиться и цитировать этот отчет

Делитесь версионным отчетом об оценке, нейтральным значком, встраиваемой карточкой и цитатами. Skillstore публикует доказательства, не решая, безопасен ли этот Skill.

Открыть версионный отчет

Копировать ссылку на отчёт

https://skillstore.io/skills/alvolutionor-pr-to-slack/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Значок Markdown

[![Skillstore security assessment](https://skillstore.io/badges/skills/alvolutionor-pr-to-slack/security.svg)](https://skillstore.io/skills/alvolutionor-pr-to-slack?utm_source=security_passport_badge)

Значок HTML

<a href="https://skillstore.io/skills/alvolutionor-pr-to-slack?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/alvolutionor-pr-to-slack/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Встраиваемая карточка

<iframe src="https://skillstore.io/embed/skills/alvolutionor-pr-to-slack.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Академические ссылки (APA · BibTeX · CFF)

Цитата APA

alvolutionor. (2026). pr-to-slack security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/alvolutionor-pr-to-slack/audits/1

Цитата BibTeX

@techreport{alvolutionor-alvolutionor-pr-to-slack-2026,
  author = {alvolutionor},
  title = {pr-to-slack security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/alvolutionor-pr-to-slack/audits/1},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "pr-to-slack security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
  - name: "alvolutionor"
date-released: "2026-10-15"
url: "https://skillstore.io/skills/alvolutionor-pr-to-slack/audits/1"
identifiers:
  - type: other
    value: "skillstore:alvolutionor-pr-to-slack:audit:1"
    description: "Skillstore immutable audit report identifier"

Оценка Skillstore

Почему такая оценка Достоверность доказательств: Средний

Архитектура

Сопровождаемость

Контент

Сообщество

Соответствие спецификации

Что вы можете построить

Prepare a release batch

Preview related repository changes, verify published commits, and prepare reviewer assignments before authorized pull request creation.

Publish a feature pull request

Create or reuse a Bitbucket pull request, preserve existing reviewers, and return its verified URL and commit information.

Integrate a review bot

Adapt the example review protocol and replace plaintext identity parsing before enabling team announcement automation.

Попробуйте эти промпты

Preview one pull request

Preview a pull request for repository [path], targeting [base branch]. Report branch commits and required reviewers. Do not create pull requests or send messages.

Create a reviewed pull request

Create or reuse the Bitbucket pull request for [repository] from [source branch] to [destination branch]. Assign configured reviewers and report the verified URL. Do not send Slack messages.

Request a correlated review

Request one Slack review for these verified pull requests: [URLs]. Inspect existing requests first and reuse an identical valid thread. Return the thread link without announcing.

Validate an announcement gate

Inspect review thread [link] for pull requests [URLs]. Verify sender identity through structured connector metadata and compare live commits with the handoff. Report any announcement blockers without sending.

Лучшие практики

Preview first and describe only changes and validation that match the published commits.
Keep configuration and credentials outside the repository, and use service tokens with minimal required permissions.
Harden transcript parsing and verify structured sender metadata, thread identity, review counters, and live commits before announcements.

Избегать

Do not treat a plaintext sender header, human approval, or completed status as proof of a clean review.
Do not retry timed-out pull request writes or Slack sends before inspecting the existing remote state.
Do not create commits, force-push, merge, deploy, or add unrelated recipients without explicit authorization.

Часто задаваемые вопросы

What services and tools are required?

The workflow requires Bitbucket Cloud, Git, Python 3.10+, requests, private configuration, service credentials, and connected Slack tools.

Do the Python helpers send Slack messages?

No. They prepare pull requests and evaluate saved review snapshots. The assistant uses connected Slack tools for messaging.

Does preview mode change remote state?

No. Preview mode reads local Git and Bitbucket state and returns a plan without creating or updating pull requests.

Is the bundled parser ready for automatic announcements?

No. Human message content can forge trusted sender headers in plaintext snapshots. Replace that identity handling and adapt the example bot protocol first.

What happens when findings remain?

Recognized findings or uncertain results block announcements. The workflow reports the reason and does not automatically repair code.

Does it merge or deploy reviewed changes?

No. Pull request delivery and review coordination do not authorize merges, deployments, new commits, or force-pushes.