git-researcher

Included with Lifetime

$97 forever

Analyze git history to trace code evolution, identify contributors, and understand commit patterns. Use for archaeological analysis of repositories. Triggers on git history, blame analysis, code evolution, contributor mapping, commit patterns.

General

What this skill does


# Git Researcher

**Audience:** Developers needing to understand how and why code evolved to its current state.

**Goal:** Analyze git history to trace code evolution, identify contributors, and extract patterns that inform current development decisions.

## Key Commands

| Purpose | Command |
|---------|---------|
| File history (recent) | `git log --follow --oneline -20 <file>` |
| Code origin tracing | `git blame -w -C -C -C <file>` |
| Pattern search in commits | `git log --grep="<keyword>"` |
| Contributor mapping | `git shortlog -sn -- <path>` |
| Code introduction/removal | `git log -S"<pattern>" --oneline` |
| Co-changed files | `git log --name-only --oneline -- <file>` |

## Analysis Methodology

1. **Start broad** - File history overview before drilling into specifics
2. **Identify patterns** - Look for themes in both code changes and commit messages
3. **Find turning points** - Significant refactorings or architecture shifts
4. **Map expertise** - Connect contributors to their domains based on commits
5. **Extract lessons** - Past issues and how they were resolved

## Analysis Dimensions

| Dimension | What to Look For |
|-----------|-----------------|
| Change context | Feature additions vs bug fixes vs refactoring |
| Change frequency | Rapid iteration vs stable periods |
| File coupling | Files that always change together |
| Pattern evolution | How coding practices changed over time |

## Output Format

```markdown
## Timeline of File Evolution
- [Date]: [Purpose of change]

## Key Contributors and Domains
- [Contributor]: [Areas of expertise]

## Historical Issues and Fixes
- [Pattern of problems and resolutions]

## Change Patterns
- [Recurring themes, refactoring cycles, architecture evolution]
```

Files: 1

Size: 2.0 KB

Complexity: 6/100

Category: General

Source: https://github.com/majesticlabs-dev/majestic-marketplace/tree/main/plugins/majestic-engineer/skills/git-researcher

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