CtrlK
BlogDocsLog inGet started
Tessl Logo

stage

Stage files, run pre-commit, fix failures, loop until clean

75

1.00x
Quality

83%

Does it follow best practices?

Impact

67%

1.00x

Average score across 1 eval scenario

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Stage Changes

Step 1: Identify Changed Files

  1. Run git status to see all changed and untracked files.
  2. Exclude from staging: .env files, credentials, secrets, large binaries.

Step 2: Stage Files

  1. git add all relevant changed files.

Step 3: Pre-commit Loop

Run up to 5 iterations:

  1. Run pre-commit run --all-files.
  2. If it passes, proceed to Step 4.
  3. If it fails:
    • Read the failure output.
    • Fix the issues.
    • Re-stage any modified files with git add.
    • Go back to step 1.
  4. If still failing after 5 attempts, report the failure details to the user and stop.

Step 4: Report

  • List what is staged: git diff --cached --name-only
  • Confirm pre-commit passes.
  • "All files staged and pre-commit clean. Ready for commit."
Repository
PaloAltoNetworks/shifter
Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.