skills.rest
lilmuckers
lilmuckersCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

agent-identities

Enforce per-archetype Git identity and posting signatures for commits and PR updates.

Updated Apr 1, 2026
Search Tags:#git#commit#pr#identity#comment#archetype#authorship
One-click install
npx skills add https://github.com/lilmuckers/agentic-team-plugin --skill agent-identities
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-identities
Source: https://github.com/lilmuckers/agentic-team-plugin/tree/main/skills/agent-identities
Command: npx skills add https://github.com/lilmuckers/agentic-team-plugin --skill agent-identities

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures that every commit and GitHub post clearly identifies the agent archetype and author, improving traceability and accountability across delivery workflows.

Core Features & Use Cases

  • Enforce per-archetype Git identity in commits and PR updates.
  • Standardize posting signatures for issue and PR comments.
  • Seamless integration with the operator config to keep identity consistent across automation and human reviews.

Quick Start

Configure your framework to begin applying per-archetype identity rules to commits and posting signatures.

Frequently Asked Questions about agent-identities

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

FAQPage Schema
How do I enforce agent identity in git commits for better attribution?▼

You can enforce agent identity in git commits by applying a defined per-archetype Git identity format. This ensures clear authorship attribution and traceability across software delivery workflows.

What is a posting signature protocol for PR and issue comments?▼

A posting signature protocol standardizes how agents identify themselves in issue and PR comments. It applies a visible signature format that can be enforced by automation and reviewed during code collaboration.

How do I standardize commit authorship across different team archetypes?▼

You standardize commit authorship by applying per-archetype Git identity rules within your operator config. This keeps agent identity consistent across automation and human reviews for all archetypes.

Do I need any dependencies to apply agent identity rules to commits?▼

No dependencies are required to apply agent identity rules to commits. The skill integrates seamlessly with your existing operator config to enforce identity formats and posting signatures.

Can automation enforce posting signatures for issue comments?▼

Yes, automation can enforce posting signatures for issue comments. The protocol implements a visible signature format designed to be enforced by automation and reviewed during collaboration audits.

Why use per-archetype Git identity instead of a single author account?▼

Using per-archetype Git identity instead of a single author account improves attribution and accountability. It distinguishes which agent archetype performed each commit, PR update, or issue comment.

Related Skills

Explore More Software Engineering Skills→
Knuckles-TeamKnuckles-Team
2

git-config

Read, set, and validate Git config values across global and local scopes.

Official
Intermediate
hicucuhicucu
1

weekly-commits

Aggregate git commit history into structured markdown reports by timeframe and author.

Community
Intermediate
jls42jls42
1

helping-with-commits

Create Conventional Commits with project scopes and pre-commit validation.

Community
Intermediate
julianobarbosajulianobarbosa
7

Commit

Automate Git commits with pre-commit security scans and Conventional Commits enforcement.

Community
Advanced