update-github
The update-github command stages uncommitted changes, creates a commit using Conventional Commits format by analyzing file modifications to determine type and scope, and pushes to the GitHub remote repository. Use this when ready to save and upload work to GitHub, with optional flags to amend previous commits, skip hooks, or specify custom commit messages.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/Galaxy-Dawn/claude-scholar/HEAD/commands/update-github.md -o ~/.claude/commands/update-github.mdupdate-github.md
# Update GitHub
Commit uncommitted changes and push to remote GitHub repository.
## Instructions
1. **Check Git Status**
- Run `git status`
- Show all uncommitted changes
2. **Analyze Changes**
- Review changed files
- Determine commit type (feat/fix/docs/refactor/test/chore)
- Determine scope (affected module/component)
3. **Create Commit Message**
Follow Conventional Commits format:
```
<type>(<scope>): <subject>
<body>
<footer>
```
Types:
- `feat`: 新功能
- `fix`: Bug 修复
- `docs`: 文档更新
- `refactor`: 代码重构
- `perf`: 性能优化
- `test`: 测试相关
- `chore`: 其他修改
4. **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
5. **Push to Remote**
- Run `git push`
- If rejected, pull with rebase first:
```bash
git pull --rebase origin $(git branch --show-current)
git push
```
6. **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.Expert code review specialist. Proactively reviews code for quality, security, and maintainability. Use immediately after writing or modifying code. MUST BE USED for all code changes.
Use this agent when the user provides a Kaggle competition URL or asks to learn from Kaggle winning solutions. Examples:
Use this agent when the user asks to "conduct literature review", "search for papers", "analyze research papers", "identify research gaps", "review related work", or mentions starting a research project. This agent integrates with Zotero for automated paper collection, organization, and full-text analysis. Examples:
Use this agent when the user provides a research paper (PDF/DOCX/arXiv link) or asks to learn writing patterns from papers, extract venue-specific writing signals, study paper structure, or mine rebuttal strategies. The agent writes extracted knowledge into the active installed paper-miner writing memory for ml-paper-writing. It does not maintain project-specific writing memory.
Use this agent when the user asks to "write rebuttal", "respond to reviewers", "analyze review comments", or needs help with academic paper review response. This agent specializes in systematic rebuttal writing with professional tone and structured responses.
Test-driven development guide for writing tests first, implementing the smallest passing change, and keeping verification tight. Use when the user explicitly wants TDD or when a task should be driven by failing tests before code.
Run a blocker-first post-experiment workflow: validate evidence, produce strict statistical analysis when possible, and generate a decision-oriented results report only when the analysis bundle is sufficient. Uses results-analysis + results-report as a gated two-stage workflow.
Commit changes following Conventional Commits format (local only, no push).