swell-agents/coding-skills / skills/committing-changes
committing-changes
VerifiedCommit via feature branch + PR + git hooks; never push main, never merge.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.5 KB |
| reference/commit-md-original.md | markdown | 1.5 KB |
| reference/git-rule.md | markdown | 670 B |
| reference/hook-troubleshooting.md | markdown | 2.3 KB |
| scripts/commit-msgexecutable | script | 1006 B |
| scripts/install-hooks.shexecutable | script | 747 B |
| scripts/install-pr-size-workflow.shexecutable | script | 1.4 KB |
| scripts/pre-commitexecutable | script | 1.2 KB |
| scripts/pre-pushexecutable | script | 504 B |
| templates/gitattributes.example | other | 672 B |
| templates/pr-size.yml | config | 1.4 KB |
scripts/install-hooks.sh
View on GitHub#!/bin/bash
# Install git hooks to the current repo's git dir.
# Works from any directory: root repo, submodule, or worktree.
# Idempotent: skips hooks that are already up to date.
SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
HOOKS_DIR="$(git rev-parse --git-dir)/hooks"
mkdir -p "$HOOKS_DIR"
CHANGED=0
for HOOK in pre-push commit-msg; do
if [[ -f "$HOOKS_DIR/$HOOK" ]] && diff -q "$SCRIPT_DIR/$HOOK" "$HOOKS_DIR/$HOOK" > /dev/null 2>&1; then
continue
fi
cp "$SCRIPT_DIR/$HOOK" "$HOOKS_DIR/$HOOK"
chmod +x "$HOOKS_DIR/$HOOK"
echo " Installed: $HOOK"
CHANGED=1
done
if [[ $CHANGED -eq 0 ]]; then
echo "Git hooks already up to date."
else
echo "Done. Git hooks installed successfully."
fi
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |