Skip to content

swell-agents/coding-skills / skills/committing-changes

committing-changes

Verified

Commit via feature branch + PR + git hooks; never push main, never merge.

FileKindSize
SKILL.mdskill md4.5 KB
reference/commit-md-original.mdmarkdown1.5 KB
reference/git-rule.mdmarkdown670 B
reference/hook-troubleshooting.mdmarkdown2.3 KB
scripts/commit-msgexecutablescript1006 B
scripts/install-hooks.shexecutablescript747 B
scripts/install-pr-size-workflow.shexecutablescript1.4 KB
scripts/pre-commitexecutablescript1.2 KB
scripts/pre-pushexecutablescript504 B
templates/gitattributes.exampleother672 B
templates/pr-size.ymlconfig1.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
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 implementationStars: 321kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 321kUpdated Claude CodeCodexVerifiedInstall
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 fallbackStars: 321kUpdated Claude CodeCodexVerifiedInstall
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 alwaysStars: 321kUpdated Claude CodeCodexVerifiedInstall