code-cycle-toolkit

Plugin code-cycle-toolkit in datacas/code-cycle-toolkit. Commands read from the repo's manifest — yesterday.

Skills (16)

• cc-code-review

  Use this skill to review a set of code changes for bugs, regressions, maintainability problems, inconsistencies, and missing tests, working from the accumulated diff against the base branch. It suits diffs, branches, and post-fix passes where a full pull-request review is not needed, and it does not

• cc-host-permissions

  Show, apply, validate, and revert the opt-in global host permissions for interactive Claude Code and Codex sessions - a conservative set that allows only reading and Git queries and denies force-pushes, merges, and branch or remote-ref deletion, with marked, reversible entries and a backup. Explains

• cc-implement-issue

  Use this skill when asked to implement a work item from GitHub Issues, Plane, or Jira and take it through a tested commit and pull request on GitHub or Bitbucket, including resolving provider context, following project instructions, and reporting the result without merging it.

• cc-initial-review

  Use this skill for a manual or orchestrated initial change-request review on GitHub or Bitbucket that must compare the full diff with its base, apply project review and conditional security triage, validate findings by execution, report checks, publish one consolidated comment, and optionally return

• cc-issue-review

  Use this skill to decide, before any implementation starts, whether a GitHub, Plane, or Jira work item is ready to implement, by comparing it and its linked work with the current repository and returning READY, NEEDS_REFINEMENT, or BLOCKED with evidence, confidence, and suggested issue edits. It is

• cc-orca-orchestrator

  Use this skill to run the complete supervised pull-request review cycle for a GitHub, Plane, or Jira work item with Orca orchestration, dispatching an implementer and a reviewer through cc-initial-review, cc-resolve-comments, and cc-rereview on GitHub or Bitbucket, interpreting each structured resul

• cc-orchestrator

  Use this skill to run the complete Code Cycle from a GitHub, Plane, or Jira work item through implementation, pull-request review, targeted resolution, and rereview on GitHub or Bitbucket, using known host delegation such as optional Claude-to-Codex review handoffs or a sequential fallback without m

• cc-pr-review

  Use this skill to perform the review criteria pass over a GitHub or Bitbucket change request, comparing the accumulated diff against its base branch and judging scope, correctness, regressions, data changes, architecture, tests, and operational risk. It produces findings and a verdict without modify

• cc-profile-config

  Show, choose, and write the Code Cycle routing profiles of the current repository - which executor, provider, model, and effort serve each role, marked as configured or default. Offers balanced cross-vendor presets where the vendor that implements never reviews its own work, toolkit defaults, single

• cc-provider-bootstrap

  Resolve and validate the issue provider and code host before a Code Cycle starts, asking only for missing values, persisting non-secret project configuration with confirmation, and caching read-only provider health checks for later runs.

• cc-rereview

  Use this skill manually or as an orchestrated task when a GitHub or Bitbucket change request changed after review and needs stable finding IDs, real verification of previous fixes, a complete accumulated rereview, regression detection, conditional security audit, current check status, an updated com

• cc-resolve-comments

  Use this skill manually or as an orchestrated task to recover stable change-request findings on GitHub or Bitbucket, triage real review feedback, implement valid targeted fixes, verify every resolution, apply the project's post-change review and security workflow, update the branch when required, an

• cc-run

  Use this skill to detect how a project's applications are meant to start, bring up the required services in the right order, and confirm they are actually responding. It reports each service with its process, port, URL, and stop command, and never silently changes ports or kills processes it does no

• cc-security-review

  Use this skill to audit code changes for authentication, authorization, validation, injection, secret-exposure, and unsafe data-handling vulnerabilities, scoped to the change and its trust boundaries. It reports confirmed vulnerabilities separately from potential risks and does not modify code.

• cc-stats

  Show the Code Cycle Toolkit stats report for this repository from local telemetry - cycles, stages, first-pass approval, review verdicts, findings, fallbacks, model drift, and rules-vs-Jev comparisons. Use whenever someone asks, in any language, for toolkit or Code Cycle stats, statistics, metrics,

• cc-verify

  Use this skill to verify that code changes actually work by running static checks, tests, and real application validation, after implementing or fixing something. It reports executed commands and observed results, separates unverified items with their reasons, and never treats code inspection as ver