skills.rest
cptnfren
cptnfrenCOMMUNITY
Explore all skills by this author →
GitHub

localsetup-public-repo-identity

Apply framework-aligned repo identity to README and CONTRIBUTING sections.

3|2|Updated Dec 25, 2025
Search Tags:#template#readme#repository#contributing#identity#gitignored#local-identity
One-click install
npx skills add https://github.com/cptnfren/localsetup --skill localsetup-public-repo-identity
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: localsetup-public-repo-identity
Source: https://github.com/cptnfren/localsetup/tree/main/_localsetup/skills/localsetup-public-repo-identity
Command: npx skills add https://github.com/cptnfren/localsetup --skill localsetup-public-repo-identity

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Public repositories often lack consistent identity management for README and CONTRIBUTING files, leading to confusion and inconsistent branding across projects.

Core Features & Use Cases

  • Public repo identity pattern and governance for README and CONTRIBUTING sections.
  • Two identity sources: local-identity.mdc and framework template; identity data kept gitignored.
  • Applied to README and CONTRIBUTING edits across repos to maintain consistency.

Quick Start

Use this skill to ensure a consistent local identity by referencing a local-identity.mdc or framework template.

Frequently Asked Questions about localsetup-public-repo-identity

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

FAQPage Schema
How do I keep public repo identity consistent across multiple README and CONTRIBUTING files?▼

To keep public repo identity consistent, reference a local-identity.mdc file or framework template across repositories. This ensures README and CONTRIBUTING sections maintain unified branding.

What is a local-identity file and how does it manage repository branding?▼

A local-identity file manages repository branding by providing identity data sourced from a per-repo local-identity.mdc file. This data populates README and CONTRIBUTING sections to ensure consistent public repo identity.

How do I prevent leaking private identity data when templating README files?▼

To prevent leaking private identity data when templating README files, keep identity data gitignored. Source this information from a per-repo local-identity.mdc file instead of hardcoding it into the public repository.

Does this public repo identity template work without external dependencies?▼

Yes, this public repo identity template works without external dependencies. It relies solely on a framework template or a local-identity.mdc file to apply consistent branding to CONTRIBUTING and README files.

When should I use a framework template versus a local-identity file for repo branding?▼

Use a framework template for initial repo branding structure, and use a local-identity file for per-repo specifics. Both ensure consistent README and CONTRIBUTING identity while keeping the actual data gitignored.

Related Skills

Explore More Content & Communication Skills→
iludeilude
8

ignore-files-workflow

Synchronizes ignore entries across .gitignore and .dockerignore files.

Community
Intermediate
CruxExpertsCruxExperts
3

ls-public-repo-identity

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

Community
Basic
HyperxqHyperxq
1

lefthook

Enforce Conventional Commits and run Git hooks via Lefthook.

Community
Intermediate
KrystianYCSilvaKrystianYCSilva

markdown-expert

Create Markdown documentation with Mermaid diagrams and GFM tables.

Community
Intermediate