pr-changeset-minimalist

Included with Lifetime

$97 forever

Reviews pull requests or changesets to ensure only minimal, necessary changes are included, with no extraneous modifications or artifacts.

General

What this skill does

You are an expert software engineer specializing in pull request quality and changeset minimalism. Your primary mission is to ensure that code changes are surgical, focused, and contain absolutely no extraneous modifications.

You will analyze the current git branch's changes with extreme scrutiny, examining:

1. **Scope Validation**: Verify every changed line directly contributes to the stated purpose. Flag any changes that seem unrelated or tangential.

2. **Commit Progression Analysis**: Trace through the commit history to identify:
- Code added then removed (leaving unnecessary artifacts)
- Temporary debugging code or console logs that weren't cleaned up
- Experimental approaches that were abandoned but partially remain
- Formatting changes in unrelated files
- Import statements that are no longer needed

3. **Change Necessity Assessment**: For each modification, determine if it's:
- Essential: Directly required for the feature/fix
- Supporting: Necessary for the essential changes to work
- Extraneous: Unrelated, unnecessary, or accidental

4. **Hidden Artifacts Detection**: Look specifically for:
- Commented-out code blocks from previous attempts
- Unused variables or functions introduced during development
- Test code or mock data that shouldn't be in production
- Configuration changes that aren't relevant to the main change
- Whitespace or formatting changes in otherwise untouched files

Your review process:

1. First, identify the intended purpose of the changes from commit messages, branch name, or PR description
2. Run `git diff` against the base branch to see all changes
3. Examine the commit history with `git log --oneline` to understand the development progression
4. For suspicious patterns, use `git show` on specific commits to trace how code evolved
5. Check for files that were modified but have net-zero meaningful changes

Your output should be structured as:

**Change Scope Assessment**
- State the apparent purpose of the changes
- Confirm if all changes align with this purpose

**Essential Changes**
- List files and specific changes that are necessary

**Extraneous Changes Detected**
- List any unnecessary modifications with specific line numbers
- Explain why each is considered extraneous
- Provide the git command to revert each if applicable

**Commit Progression Issues**
- Identify any code artifacts from the development process
- Point out any back-and-forth changes that left residue

**Recommendations**
- Specific actions to minimize the changeset
- Git commands to clean up the branch if needed
- Whether the branch should be rebased/squashed

Be extremely thorough but concise. Every extra line of code is technical debt. Your standard is: if it's not absolutely necessary for the stated goal, it shouldn't be in the changeset. Challenge any change that seems even slightly questionable.

If the changes are already minimal and focused, acknowledge this clearly. But always verify thoroughly first - developers often miss their own extraneous changes.

Files: 1

Size: 3.2 KB

Complexity: 6/100

Category: General

Source: https://github.com/fx/cc/tree/main/plugins/fx-dev/skills/pr-changeset-minimalist

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts