skills.rest
PranavNagrecha
PranavNagrechaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

developer-impact-and-reachability

Analyze Salesforce org impact and reachability using metadata queries and heuristic analysis.

2|Updated Jun 17, 2026
Search Tags:#code analysis#impact analysis#test coverage#Salesforce#reachability analysis
One-click install
npx skills add https://github.com/PranavNagrecha/Salesforce-Intelligence --skill developer-impact-and-reachability
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: developer-impact-and-reachability
Source: https://github.com/PranavNagrecha/Salesforce-Intelligence/tree/main/.claude/skills/developer-impact-and-reachability
Command: npx skills add https://github.com/PranavNagrecha/Salesforce-Intelligence --skill developer-impact-and-reachability

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires sforce, python, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides detailed analysis of Salesforce org impact and reachability, helping developers understand the consequences of code changes and identify unreachable code.

Core Features & Use Cases

  • Impact Analysis: Assess the effects of changes like deactivating flows, disabling triggers, or altering field types.
  • Reachability Analysis: Determine where a method is called from and its downstream effects.
  • Test Coverage Analysis: Identify which tests cover a specific method and assess test quality.
  • Use Case: Before making a code change, use this Skill to understand potential impacts and ensure test coverage.

Quick Start

Analyze the impact of changing the 'Industry__c' field type from Text to Picklist using the 'sfi.what_if_change_field_type' command.

Frequently Asked Questions about developer-impact-and-reachability

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze the impact of changing a Salesforce field type?▼

Salesforce impact analysis assesses the consequences of code changes by querying org metadata. It helps you understand downstream effects, such as what happens when you deactivate flows or alter field types.

How do I find unreachable code in my Salesforce org?▼

Dead code detection in Salesforce is performed using reachability analysis. The tool builds a call graph to determine where a method is called from, helping you identify and safely remove unreachable code.

Can I check which tests cover a specific method before making changes?▼

Yes, test coverage analysis identifies which Salesforce tests cover a specific method. This allows you to assess test quality and ensure adequate coverage before proceeding with code modifications.

Do I need Python to run Salesforce reachability analysis?▼

Yes, Python is required to run this analysis. The tool utilizes Python libraries to query Salesforce org metadata via the sforce API and apply heuristic analysis for impact and reachability assessments.

What is the best way to trace downstream effects of disabling a trigger?▼

The best way to trace downstream effects is to use a what-if scenario analysis. It evaluates the impact of disabling triggers by mapping the call graph and identifying affected components across the org.

Related Skills

Explore More Software Engineering Skills→
PranavNagrechaPranavNagrecha
2

business-user-orientation

Translate business-user questions into Salesforce metadata insights.

Community
Advanced
xjtu-wangxjtu-wang
4

competition-queue-worker-drift

Trace enqueued items through worker processing and retries to identify asynchronous drift.

Community
Advanced
nanorepublicananorepublica
61

Testing Unit Tests

Standardize unit-test coding practices across Claude Code projects.

Community
Basic
padjeipadjei

omnistudio-dependencies-analyze

Map OmniStudio component dependencies and generate Mermaid diagrams.

Community
Advanced