Skip to content

tobihagemann/turbo / claude/skills/commit-rules

commit-rules

Unverified

Shared commit message rules and technical constraints for skills that write commits. Not typically invoked directly.

Commit Rules

Commit Message Rules

  • Match the style from git log -n 10 --oneline
  • Concise and descriptive
  • Imperative mood, present tense
  • Aim for ≤100 characters in the subject
  • No commit description—summarize everything in the message
  • Don't reference .turbo/ content (filenames, acceptance criteria, step numbers, headings) in commit messages. .turbo/ is gitignored, so these references would be opaque to anyone reading without local copies.

Technical Constraints

  • Use git commit -m "message" directly—do not use heredoc syntax (sandbox blocks temp file creation)
  • Never bypass commit signing (--no-gpg-sign, -c commit.gpgsign=false). If signing fails, use AskUserQuestion to let the user resolve it—they may need to approve a key prompt.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 464kUpdated Claude CodeCodexVerifiedInstall
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 464kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 318kUpdated Claude CodeCodexUnverifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 318kUpdated Claude CodeCodexUnverifiedInstall