A Claude Code workspace template with AI skills for JIRA, PRs, code review, estimation, and daily standups
This repository also configures its own agents. See what polaris tells them →
Skill Claude Code
Before handing your own change over — opening a PR, asking for review, saying "done" — check it against eight questions that come from what reviewers actually caught: claims that do not match the diff, the repo's own rules not applied, half-done pattern changes, runtime behaviour asserted from reading source, last…
Skill Claude Code
A tool for saving, listing, and restoring checkpoints for long coding sessions. A checkpoint records work state so a session can continue after interruption or context compression.
Skill Claude Code
Commander mode: use when one session commands the other Claude sessions on this machine — to read the map of who holds what, to dispatch work (one-to-one or a mutual review between several sessions), to watch its own stability signals, to hand the commander role to the next session, or to escalate a decision to the…
Skill Claude Code needs its repo
A workflow guide for taking a coding task from an initial request to a checked delivery. It decides whether the task needs to be formally tracked, which stage it is in, and when it is complete or blocked.
Skill Claude Code needs its repo
An implementation workflow for a coding task whose definition of success has already been agreed. It covers exploring, changing the code, measuring the result, and continuing through repeated work cycles.
Skill Claude Code
A learning workflow for turning outside material, articles, repositories, and code-review lessons into knowledge that can be used in a workspace. It also supports processing a queue of learning tasks and setting up a daily scanner.
Skill Claude Code
A manual tool for sorting saved session memories into Hot, Warm, and Cold groups, and finding memories that may be moved or retired.
Skill Claude Code
A Slack handoff workflow for pull requests. A pull request is a proposed code change for review; this workflow takes its link from Slack, sends the work to be fixed, and reports the result back in the Slack thread.
Skill Claude Code needs its repo
A first-stage workflow for agreeing on a precise definition of success for a piece of work and recording it for later checks. It also creates a small starter record when related work appears during another task.
Skill Claude Code
A workflow for finding your open GitHub pull requests and asking the right people to review them. A pull request is a proposed code change waiting for teammates to check before it is merged.
Skill Claude Code
A workflow for finding multiple team pull requests that need your review and handling them together. A pull request is a proposed code change submitted for review before merging.
Skill Claude Code
A workflow for reviewing one other person's GitHub pull request by examining its proposed code changes and project rules. It can leave comments and submit an approval or request for changes.
Skill Claude Code
A workflow for producing a daily standup report or end-of-day summary from work signals such as Git, JIRA, calendars, pull requests, planning, blockers, and the user’s own notes. A pull request is a proposed code change for review.
Skill Claude Code
A shared definition of done for software changes. It says that code should live on a branch, have a pull request, pass review before entering the default branch, and pass local checks before being pushed.
Skill Claude Code needs its repo
A final acceptance check that runs strict, recorded tests against a defined success condition. It separates automatic pass-or-fail evidence from a written report that a person interprets.
Skill Claude Code
Standalone visual regression guard using before/after screenshot comparison. Two modes: SIT (compare staging vs local dev) or Local (compare git-stashed base vs current changes). No long-lived baselines — captures fresh screenshots each run and deletes after comparison. Config-driven from workspace-config.yaml. Use…
Skill Claude Code
A workflow guide for opening issues in the framework’s own repository. It distinguishes reports of problems found during work from requests for new framework features, and defines the information each needs.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: