agentleFS
Sign inStart free
LedgerHQLedgerHQ/ledger-live/.agents/skills/slack-pr-message/SKILL.md

slack-pr-message

Skill627 starsChanged 9 days agoMITView on GitHub

Generate a formatted Slack message to share a pull request with the team. Use when the user asks to generate a Slack message for a PR, share a PR on Slack, or after creating a pull request.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When multiple non-app packages are impacted alongside an app, use the app prefix.

    line 33

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Slack PR Message

Generate a formatted Slack message to announce a pull request.

Instructions

  1. Determine the PR URL and short description from the current context (branch, PR title, or user input).
  2. Determine the correct prefix based on impacted packages.
  3. Output the formatted message.

Format

:pr-open: {{PREFIX}} - {{SHORT_DESCRIPTION}}
{{PR_URL}}

Prefix Rules

Impacted packagesPrefix
live-mobile onlyLWM
ledger-live-desktop onlyLWD
@ledgerhq/live-common or shared libs under libs/Common
CI, scripts, developer tooling, support/ presetsTooling
Both live-mobile and ledger-live-desktopLWM + LWD

When multiple non-app packages are impacted alongside an app, use the app prefix. Combine prefixes only when both apps are affected.

A package under shared/, domain/, features/ or devtools/ takes the prefix of the app(s) it reaches, not Common: @features/flow-app-unlock only ships on mobile, so a change to it is LWM. Derive the apps from the changed files with the Nx command in the run-builds skill, then narrow by platform suffix (*.web.tsx → LWD, *.native.tsx → LWM).

Example

:pr-open: LWM - Add portfolio analytics dashboard
https://github.com/LedgerHQ/ledger-live/pull/1234

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free