Separate local readiness edits from remote mutations
Separate local readiness edits from remote mutations.
Agent skill for auditing and preparing professional GitHub repositories, metadata, topics, community files, security, and CI.
A codebase can be technically ready while its Git identity, metadata, security guidance, community files, secret hygiene, and CI do not support professional public collaboration.
Visibility, repository creation, branch/settings changes, and pushes are external mutations.
Licenses and homepage URLs cannot be assumed.
Partial remote success must not trigger destructive compensation.
Local manifest/Git/community/workflow auditor; metadata and preparation rules; authorization-gated GitHub CLI/API actions with read-back verification.
Local manifest/Git/community/workflow auditor.
Metadata and preparation rules.
Authorization-gated GitHub CLI/API actions with read-back verification.
Separate local readiness edits from remote mutations.
Require an explicit visibility/license choice instead of defaults.
Verify remote settings and SHAs after changes rather than trusting mutation responses alone.
Share your challenge, scope, and timeline to start a focused conversation.