brainstorming
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).
commit-changesStage, commit, and amend changes with conventional commit messages. Covers reviewing changes, selective staging, writing descriptive commit messages using HEREDOC format, and verifying commit history. Use when saving a logical unit of work to version control, creating a commit with a conventional message, amending the most recent commit, or reviewing staged…
Independent GitHub snapshot · Automated classification · Original documentation governs
擇檔、書訊、驗史也。
查樹態、視差也:
# See which files are modified, staged, or untracked
git status
# See unstaged changes
git diff
# See staged changes
git diff --staged
得:諸變、擇、未追之檔皆明。
敗:git status 敗→驗於庫內(git rev-parse --is-inside-work-tree)。
勿用 git add . 或 git add -A,擇檔以免誤入密檔或雜變:
# Stage specific files by name
git add src/feature.R tests/test-feature.R
# Stage all changes in a specific directory
git add src/
# Stage parts of a file interactively (not supported in non-interactive contexts)
# git add -p filename
提前察擇:
git diff --staged
得:唯意之檔與變入擇。無 .env、密、巨檔也。
敗:誤入→ git reset HEAD <file> 撤。密入→立撤乃提。
用規範提交式。必以 HEREDOC 傳訊以正格:
git commit -m "$(cat <<'EOF'
feat: add weighted mean calculation
Implements weighted_mean() with support for NA handling and
zero-weight filtering. Includes input validation for mismatched
vector lengths.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
EOF
)"
規範類型:
| Type | When to use |
|---|---|
feat | 新功 |
fix | 除錯 |
docs | 僅文 |
test | 增更驗 |
refactor | 重構無增減 |
chore | 建、CI、依更 |
style | 排版空白(無邏輯變) |
得:提交成,訊述「何以」,非僅「何」也。
敗:預提鉤敗→修、重 git add、建新提交(勿 --amend,敗提未生也)。
未推共遠方可改:
# Amend message only
git commit --amend -m "$(cat <<'EOF'
fix: correct weighted mean edge case for empty vectors
EOF
)"
# Amend with additional staged changes
git add forgotten-file.R
git commit --amend --no-edit
得:前提交就地更。git log -1 示改後容。
敗:已推→勿改。建新提交代之。強推改提→史分歧。
# View the last commit
git log -1 --stat
# View recent commit history
git log --oneline -5
# Verify the commit content
git show HEAD
得:提交顯於史,訊、作者、檔變皆正。
敗:檔誤→ git reset --soft HEAD~1 撤而留擇、乃重提正。
.env)入git log 示正元git add .:必先察 git status。宜按名擇--no-edit:補忘檔入末提→用 --no-edit 存舊訊--amend:鉤敗則提未生。--amend 改前提。修鉤後必建新提manage-git-branches - 提前枝工create-pull-request - 提後下步resolve-git-conflicts - 合併/改基衝突configure-git-repository - 庫設與規