pull

Automate Git pulls with local commits and merge conflict resolution.

27|4|Updated Jun 19, 2025
One-click install
npx skills add https://github.com/markmhendrickson/neotoma --skill pull-markmhendrickson
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pull
Source: https://github.com/markmhendrickson/neotoma/tree/main/.cursor/skills/pull
Command: npx skills add https://github.com/markmhendrickson/neotoma --skill pull-markmhendrickson

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of updating your local codebase with the latest changes from a remote repository, ensuring your development environment is always current and preventing merge conflicts.

Core Features & Use Cases

  • Automated Pull: Fetches and merges the latest commits from the origin.
  • Submodule Support: Can perform pull operations on specific Git submodules.
  • Pre-Pull Commit: Automatically commits any unpushed local changes before pulling.
  • Setup Script Execution: Runs relevant setup scripts after a successful pull.
  • Use Case: Before starting your daily development, run /pull to ensure you have the latest code, commit any minor changes you made yesterday, and execute any necessary setup scripts. If you're working on a specific component, use /pull foundation to update just that submodule.

Quick Start

Run the pull skill to update the main repository with the latest changes from origin.

Frequently Asked Questions about pull

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

FAQPage Schema
How do I automate a Git pull and resolve merge conflicts?

Automating a Git pull requires a tool that fetches and merges the latest commits from origin while resolving potential merge conflicts. This Skill performs that synchronization by automatically committing local changes before pulling updates.

Can I automatically commit local changes before pulling remote updates?

Yes, you can automatically commit local changes before pulling remote updates. This ensures unpushed local modifications are safely committed to version control prior to fetching and merging the latest commits from the origin repository.

How do I execute post-pull setup scripts after updating my repository?

Executing post-pull setup scripts after updating your repository ensures your development environment is configured correctly. This Skill automatically runs relevant setup scripts after a successful pull to maintain code consistency across dependencies.

Does this Git automation support pulling specific submodules?

Yes, this Git automation supports pulling specific submodules. You can target and update individual Git submodules by specifying the submodule name, allowing you to synchronize only the required component instead of the entire repository.

What is the best way to keep my local codebase in sync with the remote repository?

The best way to keep your local codebase in sync with a remote repository is automating the pull process. Fetching, merging, and executing post-pull setup scripts ensures code consistency and prevents merge conflicts before starting daily development.