Skip to content

carapace-sh/carapace-bin / skills/git

Use when working with Git — object model, references, index, branching, merging, rebasing, remotes, diffs, config, hooks, worktrees, submodules, and plumbing commands. Triggers on: "git", "git branch", "git commit", "git merge", "git rebase", "git checkout", "git stash", "git reset", "git submodule", "git worktree", "git blame", "git bisect", "git reflog", "git hooks", "git config".

Security report

Flagged

Static analysis of one exact version. It reduces risk and shows evidence; it does not certify that a skill is safe.

Commit
1ac8bc7323d9834a239b3ab77c6cd93fddd187ef
Content hash
3dcd67b656b42fcf2d5e7d0d753a1d7b9f3e716488ac1b6ecd95bd638dceef30
Scanned
2026-11-17
Scanner version
skillxone-scan-1.0.0
Policy version
0.1-draft
Decision
1 open critical or high finding.
Verification expires
Not applicable

Findings (1 high, 1 medium)

  • highFILE-TOKEN-STORESreferences/remotes.md:256

    The skill refers to a token store or the system keychain, a location that holds private data or credentials.

    git config credential.helper store # Store in ~/.git-credentials (plaintext)

    Suggested fix: Do not read credential stores or private files. If the task needs a credential, ask the user to provide it through the environment.

    Report as false positive

  • mediumPI-IGNORE-INSTRUCTIONSreferences/internals.md:357

    The text tells the agent to ignore or override its existing instructions, a common prompt-injection pattern. Severity lowered from high because it appears in a code example.

    git check-ignore --all <path> # Show all matching rules

    Suggested fix: Remove the instruction. A skill should add guidance for its task, not cancel the instructions the agent already follows.

    Report as false positive

Checks run

  • prompt-injection
  • dangerous-commands
  • credentials
  • network
  • file-access
  • integrity

Checks skipped

  • dependencies: No dependency manifest in the skill directory.
  • gitleaks: gitleaks is not installed on this host.
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: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated 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: 322kUpdated 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: 322kUpdated Claude CodeCodexVerifiedInstall