What is update-github?

A command for committing local code changes and sending them to a GitHub repository. It uses Conventional Commits, a standard format for describing changes such as fixes, features, and documentation updates.

Use it after reviewing your changes when you want to stage, commit, push, and verify the current branch.

It turns a set of uncommitted changes into a traceable commit and keeps the remote repository up to date.

update-github — Command by Galaxy-Dawn

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add commands/galaxy-dawn/claude-scholar/update-github

Clone the repo

git clone --depth 1 https://github.com/Galaxy-Dawn/claude-scholar

Or install claude-scholar, the plugin that ships this one along with the rest of its 16 skills, 34 commands, 6 agents, 5 hooks.

Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 590 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.

Model	Per session	Once invoked
Fable 5	$0.00015	$0.00590
Opus 5	$0.00008	$0.00295
Sonnet 5	$0.00003	$0.00118
Haiku 4.5	$0.00002	$0.00059

Measured 3d ago against content hash 4b68f687041d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

update-github 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 3d ago.

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.

commands/update-github.md · 101 lines

How it starts

The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Update GitHub

Commit uncommitted changes and push to remote GitHub repository.

Instructions

Check Git Status
- Run git status
- Show all uncommitted changes
Analyze Changes
- Review changed files
- Determine commit type (feat/fix/docs/refactor/test/chore)
- Determine scope (affected module/component)
Create Commit Message Follow Conventional Commits format:
```
<type>(<scope>): <subject>

<body>

<footer>
```
Types:
- feat: 新功能
- fix: Bug 修复
- docs: 文档更新
- refactor: 代码重构
- perf: 性能优化
- test: 测试相关
- chore: 其他修改
Stage and Commit
- Run git add for affected files
- Create commit with formatted message
- Do not include Co-Authored-By footers unless the user explicitly asks for them

Push to Remote

Run git push

If rejected, pull with rebase first:

git pull --rebase origin $(git branch --show-current)
git push

Verify Success
- Show commit SHA
- Show remote branch status

Example Usage

User: /update-github

1. Checking git status...
   Modified: src/utils/helpers.py
   Modified: README.md

2. Analyzing changes...
   - src/utils/helpers.py: Refactored helper functions
   - README.md: Updated documentation

3. Proposed commit:
   docs(readme): 更新项目文档

   - 添加使用示例
   - 更新依赖说明

4. Proceed? (yes/no/modify)

5. Staging files...
   git add src/utils/helpers.py README.md

6. Creating commit...
   [main abc1234] docs(readme): 更新项目文档

7. Pushing to remote...
   git push
   To github.com:user/repo.git
      abc1234..def5678  main -> main

✅ Successfully pushed to GitHub!

Arguments

$ARGUMENTS can be:

--amend - Amend last commit instead of creating new one
--no-verify - Skip pre-commit hooks
<type>(<scope>): <message> - Use custom commit message

Integration

This command uses the same Conventional Commits format as the /commit skill but focuses on the complete flow: stage → commit → push.

Read the full file on GitHub · 101 lines

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.

3d ago First seen · 101 lines · 15 tokens per session scan A 4b68f687041d

Subscribe to this mod's changes

update-github is a command published in the GitHub repository Galaxy-Dawn/claude-scholar (5,297 stars, last pushed 6d ago), licensed MIT. It adds 15 tokens to every session and 590 once invoked, about $0.0001 per session on Opus 5. 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-08-30.

Commits Git and workflow academic-research ai-agents claude claude-code developer-tools mcp

update-github

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Update GitHub

Instructions

Example Usage

Arguments

Integration

What this file has done since we first saw it

Other commands, from other repositories

speckit.git.commit

commit-all

commit

commit

brief

commit