share-rule

The developer wants to propose a team rule. Invoke the propose-team-rule skill.

If the developer included a one-line description in $ARGUMENTS, use it as the seed for the rule title and the description: frontmatter — but still confirm the full rule wording with them before opening the PR.

If $ARGUMENTS is empty, derive the candidate rule from the recent conversation: identify the most recent insight that looks generic (a coding convention, a workflow rule, a non-obvious gotcha that applies broadly), restate it back to the developer in one or two sentences, and only proceed after they confirm.

The skill handles the rest — git worktree isolation, branch creation, PR opening, and cleanup. Surface the resulting PR URL to the developer when done.