ls-public-repo-identity

Apply local identity files or framework templates to keep sensitive data out of public repository content.

3|2|Updated Dec 25, 2025
One-click install
npx skills add https://github.com/CruxExperts/localsetup --skill ls-public-repo-identity
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ls-public-repo-identity
Source: https://github.com/CruxExperts/localsetup/tree/main/_localsetup/skills/ls-public-repo-identity
Command: npx skills add https://github.com/CruxExperts/localsetup --skill ls-public-repo-identity

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Public repository identity management keeps sensitive identity data private and out of public content by using a local identity file or a framework template.

Core Features & Use Cases

  • Provides a standard approach for referencing identity in READMEs and CONTRIBUTING guides without exposing personal or organization details.
  • Enables per-machine customization via a local-identity.mdc file or a reusable framework template across repos.
  • Supports safe, auditable edits by clearly indicating where identity information should come from.

Quick Start

Copy the template at _localsetup/config/templates/public-repo-identity.template.mdc into local-identity.mdc and fill in placeholders with your identity details.

Frequently Asked Questions about ls-public-repo-identity

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

FAQPage Schema
How do I keep my personal identity private in a public git repository README?

Keeping personal identity private in a public git repository README involves applying a local identity file or framework template. This approach substitutes sensitive details with non-identifying references during documentation edits to ensure personal data stays out of public content.

How do I configure a local-identity.mdc file for my repository workflows?

Configuring a local-identity.mdc file requires copying the public-repo-identity template from the framework config directory and filling in the placeholders. This per-machine file provides your specific identity details for safe, auditable documentation edits across repositories.

How do I standardize CONTRIBUTING guides across multiple repos without exposing organization details?

Standardizing CONTRIBUTING guides without exposing organization details is done by applying a reusable framework template across repositories. This provides a standard approach for referencing identity consistently while keeping sensitive organization data private.

What is a public repo identity template and when do I need it for documentation edits?

A public repo identity template is a file that guides non-identifying references in documentation. You need it when editing READMEs or CONTRIBUTING files to ensure sensitive identity data is replaced with safe, auditable placeholders during public content creation.

Do I need a separate local-identity file for each machine to manage repository identity?

Yes, managing repository identity requires a local-identity.mdc file per machine. This per-machine customization allows you to safely apply private identity details to repository documentation without hardcoding sensitive data into the public content.