메뉴
Squashes multiple git commits into a single commit with a clean message. Use when cleaning up commit history, combining WIP commits, preparing branches for merge, tidying feature branches, or when asked to squash, combine, or consolidate commits.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Reviews dotnet/perf-autofiling-issues and lists issues that represent WASM Mono or WASM CoreCLR regressions. Use when preparing for perf triage, scanning auto-filed performance regressions, or generating a quick browser-WASM issue report.
Analyze CI build and test status from Azure DevOps and Helix for dotnet repository PRs. Use when checking CI status, investigating failures, determining if a PR is ready to merge, or given URLs containing dev.azure.com or helix.dot.net. Also use when asked "why is CI red", "test failures", "retry CI", "rerun tests", "is CI green", "build failed", "checks failing", or "flaky tests".
A meta-skill for managing Agent Skills. Use when creating, editing, modifying, updating, deleting, or refactoring skills. Also triggers for SKILL.md files, ~/.copilot/skills/ directory, .github/skills/ folder, skill frontmatter, skill instructions, skill templates, or any file changes in a skills directory. Ensures all changes are committed and pushed to git.
Analyze VMR codeflow PR status for dotnet repositories. Use when investigating stale codeflow PRs, checking if fixes have flowed through the VMR pipeline, debugging dependency update issues in PRs authored by dotnet-maestro[bot], checking overall flow status for a repo, or diagnosing why backflow PRs are missing or blocked.
Performs comprehensive code reviews for GitHub pull requests. Use when reviewing PRs, checking if a PR fixes an issue, analyzing code changes, or when given a GitHub PR URL (github.com/.../pull/...). Evaluates problem alignment, code quality, security threats, alternative approaches, edge cases, and identifies duplicate/existing implementations.
| name | commit-squashing |
| description | Squashes multiple git commits into a single commit with a clean message. Use when cleaning up commit history, combining WIP commits, preparing branches for merge, tidying feature branches, or when asked to squash, combine, or consolidate commits. |
Helps squash multiple git commits into a single, well-structured commit to maintain a clean git history.
First, review the commits that will be squashed:
# Show last N commits with summary
git log --oneline -n 10
# Show with more detail
git log --pretty=format:"%h %s%n%b" -n 10
Choose the appropriate method based on the situation:
| Scenario | Method |
|---|---|
| Squash last N commits | Interactive rebase: git rebase -i HEAD~N |
| Squash into specific commit | Interactive rebase to that commit |
| Squash all commits on branch | Soft reset + recommit |
| Squash before merge (PR) | Merge with --squash flag |
# Replace N with number of commits to squash
git rebase -i HEAD~N
In the editor that opens:
pick for the first (oldest) commitpick to squash (or s) for commits to combine# Find the commit to reset to (usually branch point)
git merge-base main HEAD
# Soft reset preserving changes
git reset --soft <commit-hash>
# Create new squashed commit
git commit -m "feat: your squashed commit message"
# From the target branch (e.g., main)
git merge --squash feature-branch
git commit -m "feat: merged feature with squashed commits"
Follow conventional commits format:
<type>(<scope>): <subject>
<body>
<footer>
Types: feat, fix, docs, style, refactor, test, chore
Example:
feat(auth): implement OAuth2 login flow
- Add OAuth2 provider configuration
- Create login/callback endpoints
- Implement token refresh logic
- Add user session management
Closes #123
If commits were already pushed, force push is required:
# Force push with lease (safer)
git push --force-with-lease
# Or standard force push
git push --force
⚠️ Warning: Only force push on branches where you're the sole contributor, or coordinate with your team.
Situation: You made 3 commits for one feature:
abc123 wip: started login formdef456 fix: typo in validationghi789 done: login form completeCommands:
git rebase -i HEAD~3
# Change to: pick abc123, squash def456, squash ghi789
# Save and write new message
Result: Single commit with clean message.
Situation: Feature branch has 10 messy commits, need to squash before merging to main.
Commands:
# Find where branch diverged
git merge-base main feature-branch
# Returns: 1a2b3c4
# Soft reset
git reset --soft 1a2b3c4
# Create clean commit
git commit -m "feat(dashboard): add analytics dashboard
- Implement chart components
- Add data fetching hooks
- Create dashboard layout
- Add unit tests"
# Force push
git push --force-with-lease
Situation: Squash went wrong, need to recover.
Commands:
# Find the commit before rebase in reflog
git reflog
# Reset to that state
git reset --hard HEAD@{n}
--force-with-lease: Safer than --force, prevents overwriting others' workProblem: Conflicts appear during interactive rebase Solution:
# Resolve conflicts in files, then:
git add .
git rebase --continue
# Or abort and try different approach:
git rebase --abort
Problem: Can't find original commits
Solution: Use git reflog to find and recover them
Problem: Remote rejects push because history diverged
Solution: Use git push --force-with-lease (only on your own branches!)
| Action | Command |
|---|---|
| View commits | git log --oneline -n 10 |
| Interactive rebase | git rebase -i HEAD~N |
| Soft reset | git reset --soft <commit> |
| Find branch point | git merge-base main HEAD |
| Force push safely | git push --force-with-lease |
| Undo rebase | git reset --hard HEAD@{1} |
| Check reflog | git reflog |