coding-policy

Migrate a legacy tile.json plugin to the .tessl-plugin/plugin.json form. Runs `tessl plugin migrate`, renames .tileignore to .tesslignore, removes the obsolete tile.json, re-lints, then reconciles residual "tile" wording to "plugin" in the repo's prose. Use when a repo still has a tile.json (and no .tessl-plugin/plugin.json), or when the user asks to migrate / convert / modernize a tile.json plugin, move off tile.json, or adopt the plugin.json manifest form.

Structured workflow for shipping code via GitHub pull requests: PR creation, dual-lens automated review (gh-aw for `rules/*.md` compliance + Copilot for doc accuracy and cross-step consistency), merge, and branch cleanup. Covers readiness checks, version reasoning, review polling, feedback handling, and post-merge verification. Use when the user wants to open a pull request, ship code, merge a branch, or handle post-merge cleanup on GitHub.

Scaffold the `jbaruch/coding-policy` gh-aw PR review workflows into a consumer repository: copies the packaged paired workflow templates (OpenAI + Anthropic reviewers), compiles them with `gh aw`, and opens a PR. After merge, every pull request in the repo is reviewed against the latest published `jbaruch/coding-policy` rules by the reviewer whose family differs from the PR's declared author model — avoiding self-review bias per `rules/author-model-declaration.md`. Use when the user wants to add, install, enable, scaffold, set up, or wire up an automated policy review / PR reviewer / coding-policy CI reviewer in a consumer repo. Also use to upgrade, update, refresh, or pull the latest reviewer templates into a consumer repo that already has the scaffold installed — the skill switches to override mode in that case.

Use when the user asks to check, review, look at, or act on a pull request by number — "check PR 5", "review PR 12", "what's going on with PR 7", "look at this PR". Classifies the PR as same-repo or fork. Fork PRs are skipped by the gh-aw policy reviewer's fork-guard; this skill offers to adopt the fork branch into the base repo as a same-repo PR the reviewer can run on, preserving the contributor's commits. Same-repo PRs pass straight through to the existing reviewer.