agentmods.dev

sf-commit-push-pr

sf-commit-push-pr is a skill for Claude Code, Codex from divingsbysangam/salesforce-compound-engineering-plugin. It costs 66 tokens per session (517 once invoked), scanned A, original, MIT.

An automated workflow for committing Salesforce code changes, pushing the branch and opening a GitHub pull request. Salesforce is a platform where applications often include Apex code, Lightning web components and configuration files.

In plain words
What is it for?
Use it when shipping Salesforce work such as Apex, Lightning web components or related configuration, especially when the request is to commit, push and create a pull request.
Why use it?
It removes the need to handle these release steps separately and keeps the pull request focused on the actual change. It also includes Salesforce-specific deployment, testing and risk information.

Skill for Claude CodeCodex

Part of the sf-compound-engineering plugin — 54 skills, 1 agent, 1 hook, 2 MCP servers shipped together

not rated 10 today A scan 66 tokens original MIT
View the source file divingsbysangam/salesforce-compound-engineering-plugin
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/divingsbysangam/salesforce-compound-engineering-plugin/sf-commit-push-pr
Any agent
npx skills add divingsbysangam/salesforce-compound-engineering-plugin --skill sf-commit-push-pr
Clone the repo
git clone --depth 1 https://github.com/divingsbysangam/salesforce-compound-engineering-plugin

Made for: Claude Code, Codex.

Or install sf-compound-engineering, the plugin that ships this one along with the rest of its 54 skills, 1 agent, 1 hook, 2 MCP servers.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for sf-commit-push-pr

README.md
[![agentmods](https://agentmods.dev/badge/skills/divingsbysangam/salesforce-compound-engineering-plugin/sf-commit-push-pr.svg)](https://agentmods.dev/skills/divingsbysangam/salesforce-compound-engineering-plugin/sf-commit-push-pr)
Your own site
<a href="https://agentmods.dev/skills/divingsbysangam/salesforce-compound-engineering-plugin/sf-commit-push-pr"><img src="https://agentmods.dev/badge/skills/divingsbysangam/salesforce-compound-engineering-plugin/sf-commit-push-pr.svg" alt="Measured on agentmods" height="20"></a>
Per session 66 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 517 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00066 $0.00517
Opus 5 $0.00033 $0.00259
Sonnet 5 $0.00013 $0.00103
Haiku 4.5 $0.00007 $0.00052

Measured 4d ago against content hash d5b8ebcd815c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

sf-commit-push-pr scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/sf-commit-push-pr/SKILL.md · 39 lines

How it starts

The opening of the file, as written. The whole thing — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.

sf-commit-push-pr

Atomic flow: commit (using sf-commit conventions) → push → open PR (using sf-pr-description).

<feature_description> #$ARGUMENTS </feature_description>

Salesforce Angle

  • PR description includes deploy plan, test plan, and Salesforce-specific risk callouts.
  • Push refuses force-push to main/master without explicit user confirmation.
  • Skips the evidence prompt when commit message and diff are sufficient.

Interaction Method

When asking the user a question, use the platform's blocking question tool (AskUserQuestion in Claude Code, request_user_input in Codex, ask_user in Gemini). Fall back to numbered options in chat when no blocking tool is available. Ask one question at a time. Prefer concise single-select choices when natural options exist.

Procedure

This skill follows the standard sf-compound-engineering execution discipline:

  1. Understand the input — read the <feature_description> block above and any referenced files, plans, or issues.
  2. Plan a small set of phases — break the work into 2-5 ordered steps that an implementer (or another skill) can verify.
  3. Apply the Salesforce Angle notes above — these encode the platform-specific considerations (governor limits, sharing context, deploy ordering, FLS, metadata semantics) that distinguish this skill from generic counterparts.
  4. Use Salesforce-aware contexts and commands — file paths under force-app/main/default/..., test commands like sf apex run test, deploy commands like sf project deploy validate and sf project deploy start, query the org with sf data query when state inspection is needed.
  5. Surface decisions back to the user — when a step requires a choice that materially affects scope or risk, ask using the platform's blocking question tool rather than guessing.
  • Salesforce knowledge: docs/solutions/ (search via the sf-learnings-researcher agent).
  • Plugin conventions: see CLAUDE.md for frontmatter, naming, and protected-artifact rules.

Read the full file on GitHub · 39 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 4d ago First seen · 39 lines · 66 tokens per session scan A d5b8ebcd815c

Subscribe to this mod's changes

sf-commit-push-pr is a skill published in the GitHub repository divingsbysangam/salesforce-compound-engineering-plugin (10 stars, last pushed today), licensed MIT. It adds 66 tokens to every session and 517 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Git and workflow
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens