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.
curl -O https://raw.githubusercontent.com/Insight-Services-APAC/ingenious/main/.claude/commands/git/gitpull.mdgit clone --depth 1 https://github.com/Insight-Services-APAC/ingeniousWrote 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.
[](https://agentmods.dev/commands/insight-services-apac/ingenious/gitpull)<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>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.
| Model | Per session | Once 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 |
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.
What it actually says
Prompt: Pull Changes from Main Branch and Resolve Merge Conflicts
Instructions
-
Fetch the latest changes from the remote repository
git fetch origin -
Switch to main branch and pull latest changes
git checkout main git pull origin main -
Switch back to current working branch
git checkout - -
Merge main into current branch
git merge main -
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(orgit merge --continue)
- Identify conflicted files:
-
Verify the merge was successful
git status git log --oneline -10 -
Run tests to ensure everything still works
uv run pytest uv run pre-commit run --all-files -
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 differencesgit log --oneline main..HEAD- See commits unique to current branchgit 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
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.
- yesterday First seen · 94 lines · 0 tokens per session scan A 441355b35e6f
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.
Other commands, from other repositories
CHANGELOG
Command "CHANGELOG" from bytedance/UI-TARS-desktop, covering 0.4.0 2024-12-10 - add logging, 1.2.29, 1.2.28, 1.2.26 and 1.2.25.
commit
智能生成 Git 提交信息并提交.
bump-plugin
Bump changed plugin and marketplace version.
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.
branch-cleanup
Clean up merged and stale branches locally and remotely.
commit
Act as a senior software engineer to commit changes to the repository in non-interactive modes ONLY, using the following template.