ingenious: Command for Claude Code

.claude/commands/git/gitpull.md

gitpull is a command for Claude Code from Insight-Services-APAC/ingenious. It costs 0 tokens per session (536 once invoked), scanned A, original, MIT.

A command workflow for updating a working Git branch with the latest changes from the main branch and resolving merge conflicts.

In plain words
What is it for?
Use it to fetch and merge main, resolve conflicting files, run tests and pre-commit checks, and push the updated branch.
Why use it?
It reduces the risk of integrating stale code and provides steps for finding conflict markers, checking the result, and running verification commands.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is Insight-Services-APAC/ingenious's own configuration. It tells Claude Code how to work on ingenious itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything ingenious configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Insight-Services-APAC/ingenious. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Insight-Services-APAC/ingenious/main/.claude/commands/git/gitpull.md
Clone the repo
git clone --depth 1 https://github.com/Insight-Services-APAC/ingenious

Made for: Claude Code.

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 gitpull

README.md
[![agentmods](https://agentmods.dev/badge/commands/insight-services-apac/ingenious/gitpull.svg)](https://agentmods.dev/commands/insight-services-apac/ingenious/gitpull)
Your own site
<a href="https://agentmods.dev/commands/insight-services-apac/ingenious/gitpull"><img src="https://agentmods.dev/badge/commands/insight-services-apac/ingenious/gitpull.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 536 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.1 $0.00000 $0.00536
Opus 5 $0.00000 $0.00268
Sonnet 5 $0.00000 $0.00107
Haiku 4.5 $0.00000 $0.00054

Measured yesterday against content hash 441355b35e6f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

gitpull 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 yesterday.

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.

.claude/commands/git/gitpull.md · 94 lines

What it actually says

Prompt: Pull Changes from Main Branch and Resolve Merge Conflicts

Instructions

  1. Fetch the latest changes from the remote repository

    git fetch origin
    
  2. Switch to main branch and pull latest changes

    git checkout main
    git pull origin main
    
  3. Switch back to current working branch

    git checkout -
    
  4. Merge main into current branch

    git merge main
    
  5. If merge conflicts occur:

    • Identify conflicted files: git status
    • Open each conflicted file and resolve conflicts manually
    • Look for conflict markers: <<<<<<<, =======, >>>>>>>
    • Edit files to resolve conflicts, keeping the desired changes
    • Stage resolved files: git add <resolved-file>
    • Continue the merge: git commit (or git merge --continue)
  6. Verify the merge was successful

    git status
    git log --oneline -10
    
  7. Run tests to ensure everything still works

    uv run pytest
    uv run pre-commit run --all-files
    
  8. Push the updated branch

    git push origin <current-branch-name>
    

Conflict Resolution Tips

  • Understanding conflict markers:

    • <<<<<<< HEAD - Your current branch changes
    • ======= - Separator
    • >>>>>>> main - Main branch changes
  • Common resolution strategies:

    • Keep both changes (merge them logically)
    • Keep only main branch changes
    • Keep only current branch changes
    • Create a new solution that combines the best of both
  • Tools to help:

    • git diff - See differences
    • git log --oneline main..HEAD - See commits unique to current branch
    • git log --oneline HEAD..main - See commits unique to main

Example Workflow

# Fetch latest changes
git fetch origin

# Update main branch
git checkout main
git pull origin main

# Go back to feature branch
git checkout feature/my-feature

# Merge main into feature branch
git merge main

# If conflicts occur, resolve them then:
git add .
git commit -m "Resolve merge conflicts with main"

# Run tests
uv run pytest

# Push updated branch
git push origin feature/my-feature
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. yesterday First seen · 94 lines · 0 tokens per session scan A 441355b35e6f

Subscribe to this mod's changes

gitpull is a command published in the GitHub repository Insight-Services-APAC/ingenious (24 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 536 tokens. 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-09-04.