ca-checkpoint
From the author
Periodic multi-reviewer sweep of the whole codebase — surfaces a triaged checkpoint report.
Install
npx skills add arbiterForge/codeArbiter --skill ca-checkpoint -a claude-code
Installs to .claude/skills/ca-checkpoint/ · Each command fetches the skill straight from GitHub with the open skills CLI.
No download: this skill’s licence (AGPL-3.0) does not let us redistribute its files. The install commands fetch them from GitHub instead.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 82
Security100
Provenance66
Maintenance100
Licence80
Adoption37
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- ca-reviewarbiterForge/codeArbiterReview a diff with the reviewer fleet, funneled to one triaged verdict. Targets the current working diff, a path, or an inbound GitHub PR.Engineering★ 149
- code-reviewanthropics/knowledge-work-pluginsReview code changes for security, performance, and correctness. Trigger with a PR URL or diff, "review this before I merge", "is this code safe?", or when checking a change for N+1 queries, injection risks, missing edge cases, or error handling gaps.OfficialEngineering★ 33.5K
- code-review-checklisttranhieutt/software_development_departmentProvides a comprehensive code review checklist for pull requests covering security, performance, maintainability, and testing. Use as a reference during code reviews or when the user asks for a review checklist.Engineering★ 74
- assessmentnotque/vexjoy-agentAssessment: read-only inspection, codebase overview, value analysis, health checks, ADR consultation, decision analysis, multi-perspective critique.Other★ 443
- critical-code-reviewerposit-dev/skillsRigorously review code or pull requests for correctness, security, accessibility, maintainability, tests, and edge cases. Use when users request a critical code review, want a guided walkthrough of findings, need implementer-facing feedback, or want to prepare, create, or submit a GitHub pull request review.Engineering★ 550
- reviewdzhng/skillsCloseout pass on a finished substantive change — sequence refactor-clean (shape), code-review (diff), and write-docs (docs) so all three run, in the order where each feeds the next. Use after implementing a slice or feature and before calling it done or committing; when the user asks for a final review, a cleanup-and-document pass, or to "review everything." For a diff-only audit, reach code-review directly.Engineering★ 1.4K
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in