claude-import-verifying-identity

Verifies repositories, branches, hosts, and deployment targets before consequential operations.

Updated Aug 25, 2017
One-click install
npx skills add https://github.com/loki495/dotfiles --skill claude-import-verifying-identity-loki495
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: claude-import-verifying-identity
Source: https://github.com/loki495/dotfiles/tree/main/ai/codex-skills/claude-import-verifying-identity
Command: npx skills add https://github.com/loki495/dotfiles --skill claude-import-verifying-identity-loki495

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Acting on the wrong repository, branch, host, container, or deployment target can cause costly and hard-to-reverse mistakes. This Skill forces an identity verification step before any consequential operation so destructive or irreversible actions land on the intended target. ## Core Features & Use Cases - Target Verification: Confirms the correct repository, branch, host, container, and deployment target before executing operations. - Delegation to a Canonical Skill: Loads and applies the full verification procedure from the verifying-identity skill in the dotfiles repository. - Use Case: Before running a database migration or deploying to a production server, the agent first confirms it is on the correct branch and connected to the intended host, preventing accidental changes to the wrong environment. ## Quick Start Ask the agent to verify the current repository, branch, and host before deploying the application to production.

Frequently Asked Questions about claude-import-verifying-identity

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify the deployment target before running a migration?▼

Confirm the current repository, branch, host, and container match the intended target before executing the migration. This Skill loads a verification procedure that checks each identity element so the operation only runs against the correct environment.

What should be checked before a destructive git operation?▼

Check the active repository path and current branch before any destructive git operation such as force-push or reset. Verifying these identifiers prevents applying irreversible changes to the wrong repository or branch.

Does this Skill contain its own verification logic?▼

No, it acts as an import wrapper that reads the canonical verifying-identity SKILL.md from the dotfiles repository and applies those instructions. The full procedure lives in the referenced file, not in this directory.

When should target verification be skipped?▼

Verification can be skipped for read-only or easily reversible local actions where a wrong target carries no cost. It is intended specifically for consequential operations like deployments, migrations, and deletions.