How-to

Set up your repository with /corpole:init

The repository kit tells Claude Code that CorPole comes first, and adds the team settings and — for GitHub or GitLab — the change-request template and CI check.

For: Team developer, Project lead

What it writes

  • A CLAUDE.md section that ranks Authority records above documents in the repository.
  • .claude/settings.json that offers the plugin to the team and turns the agent policy into permission rules (ask / deny).
  • Optionally, on GitHub, a PR template and a GitHub Action; on GitLab, a merge request template and .gitlab/corpole.yml to include from .gitlab-ci.yml. Both check cited record codes and the changed files, and report test results.

Steps

  1. Run /corpole:init in the repository; it reads the origin remote to choose GitHub or GitLab.
  2. Review the files it shows; it merges with what is there.
  3. Commit them. For the check, add CORPOLE_TOKEN with a service token: a repository secret on GitHub, a masked CI/CD variable on GitLab (and the include: line in .gitlab-ci.yml).
  4. Connect the repository in Solution settings → Repositories and CI, choose the component it belongs to (a monorepo folder can belong to its own component), and add the webhook it shows with that repository's secret.
  5. The check keeps one CorPole comment on each pull request up to date (GitHub, with the repository's own token). On GitLab, add the optional masked variable CORPOLE_GITLAB_TOKEN (a solution access token with the Reporter role and the api scope) for the same note on merge requests.

Feedback for CorPole