Skip to content
cccskills
FreePublished on GitHub

gitrules

Critical Git safety rules to prevent destructive operations. Use whenever performing git operations, reverting changes, or managing commits. Prevents accidental loss of work.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md1.9 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Critical Git Safety Protocol

NEVER USE git checkout TO REVERT CHANGES.

MANDATORY GIT SAFETY RULES:

  • NEVER run git checkout -- <file> without first examining what you're about to destroy
  • ALWAYS use git diff <file> to see exactly what changes will be lost
  • MANUALLY undo changes by editing files to revert specific problematic sections
  • Preserve valuable work: if user says changes are bad, ask which specific parts to revert
  • git checkout destroys ALL changes: this can eliminate hours of valuable progress
  • When user asks to "undo" changes: Read the current file, identify problematic sections, and manually edit to fix them

Why this matters: Using git checkout blindly can destroy sophisticated implementations, complex prompts, provider-specific logic, and other valuable work that took significant time to develop.

Git Safety Rules

NEVER run these commands without explicit user approval:

  • git reset --hard: Destroys uncommitted changes permanently
  • git checkout -- .: Discards all working directory changes
  • git clean -fd: Deletes untracked files permanently
  • git stash drop: Deletes stashed changes

ALWAYS before any git operation:

  1. Run git status first to check for uncommitted changes
  2. If there are uncommitted changes, STOP and ASK the user before proceeding
  3. Suggest git stash to preserve changes if needed
  4. Never create a commit unless the user explicitly asked for one

If user asks to "revert" something:

  1. First clarify: revert committed changes or uncommitted changes?
  2. Show what will be affected before doing anything
  3. Get explicit confirmation for destructive operations

This rule exists because careless git operations destroyed 2 days of work.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

adapt

Free

Adapt designs to work across different screen sizes, devices, contexts, or platforms. Implements breakpoints, fluid layouts, and touch targets. Use when the user mentions responsive design, mobile layouts, breakpoints, viewport adaptation, or cross-device compatibility.

The English summary is being prepared. Showing the original description.

waynesutton/agent-ready-component9Updated Aug 28, 2026

Agent Ready project design context for navigation, docs links, and interface tone. Use when building or reviewing UI in this repo so patterns match the documented product feel.

The English summary is being prepared. Showing the original description.

waynesutton/agent-ready-component9Updated Aug 28, 2026

Review a feature and enhance it with purposeful animations, micro-interactions, and motion effects that improve usability and delight. Use when the user mentions adding animation, transitions, micro-interactions, motion design, hover effects, or making the UI feel more alive.

The English summary is being prepared. Showing the original description.

waynesutton/agent-ready-component9Updated Aug 28, 2026

Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy. Use when the user mentions layout feeling off, spacing issues, visual hierarchy, crowded UI, alignment problems, or wanting better composition.

The English summary is being prepared. Showing the original description.

waynesutton/agent-ready-component9Updated Aug 28, 2026

audit

Free

Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review.

The English summary is being prepared. Showing the original description.

waynesutton/agent-ready-component9Updated Aug 28, 2026

bolder

Free

Amplify safe or boring designs to make them more visually interesting and stimulating. Increases impact while maintaining usability. Use when the user says the design looks bland, generic, too safe, lacks personality, or wants more visual impact and character.

The English summary is being prepared. Showing the original description.

waynesutton/agent-ready-component9Updated Aug 28, 2026

See all skills by waynesutton

Report a problem with this skill