arrive-reviewability
Rules and workflows for maintaining reviewable and bounded code changes.
Install
mkdir -p .claude/skills/arrive-reviewability && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/16747" && unzip -o skill.zip -d .claude/skills/arrive-reviewability && rm skill.zipInstalls to .claude/skills/arrive-reviewability
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Rules for maintaining reviewable code changesKey capabilities
- →Isolate refactoring commits from behavior changes
- →Separate database/schema changes into distinct PRs
- →Isolate security-sensitive code changes
- →Split changes by ARRIVE component
- →Attach verification evidence to the Advance
- →Track estimated and actual review time
How it works
The rules guide developers to make smaller, focused changes and to capture verification evidence based on the change type. It uses `arrive score` output to inform checkpointing decisions.
Inputs & outputs
When to use arrive-reviewability
- →Split PRs by component
- →Isolate refactors
- →Prepare for code reviews
About this skill
Reviewability Rules
Keep changes bounded and reviewable. TDD/Tidy First sequence: arrive-dev-practices.mdc. Budget thresholds: arrive-core.mdc.
Smaller, Bounded Edits
Prefer smaller, focused changes:
- Isolate tidying - Refactoring commits separate from behavior changes
- Isolate migrations - Database/schema changes in separate PRs
- Isolate auth changes - Security-sensitive code separately
- Separate interface from implementation - Public API changes vs internal refactors
- Split by ARRIVE component - When touching multiple components
Review-Time Usage
- Treat review-time estimate as a planning signal, not a vanity metric.
- Use
arrive scoreoutput to decide checkpointing:- Green: proceed, optional split
- Yellow: split at natural tidy/test/feat boundaries
- Red: split before continuing implementation
- Track estimated and actual review time in the Advance frontmatter and adjust future split strategy when estimates are consistently off.
Evidence Capture
Always run the fastest verification that matches change type:
| Change Type | Required Evidence |
|---|---|
| Logic change | Unit tests (TDD) |
| API change | Integration tests (TDD) |
| UI change | Visual/E2E tests |
| Config change | Lint/validation |
| Tidying | Existing tests still pass |
Attach evidence to the Advance.
Risk Signals
Watch for these risk flags:
resident_touched- Resident component modifiedmigration- Database/schema changesauth- Authentication/authorization changesconcurrency- Threading/async changescaching- Cache invalidation changespublic_api- Public interface changesnew_dependency- New external dependency
Each flag increases reviewability score.
When not to use it
- →When the task involves editing the canonical source under `arrive/agent-rules/` or `arrive/agent-commands/`
- →When the task is to hand-edit generated files
Limitations
- →The rules apply to maintaining reviewable code changes
- →The rules are generated and not meant for hand-editing
How it compares
This workflow provides specific guidance on how to bound changes and capture evidence, unlike a manual approach that might lack structured advice for reviewability.
Compared to similar skills
arrive-reviewability side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| arrive-reviewability (this skill) | 0 | 2mo | No flags | Intermediate |
| resolve-conflicts | 81 | 8mo | Review | Intermediate |
| dependency-upgrade | 26 | 5mo | Review | Intermediate |
| git-commits | 21 | 4mo | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
resolve-conflicts
antinomyhq
Use this skill immediately when the user mentions merge conflicts that need to be resolved. Do not attempt to resolve conflicts directly - invoke this skill first. This skill specializes in providing a structured framework for merging imports, tests, lock files (regeneration), configuration files, and handling deleted-but-modified files with backup and analysis.
dependency-upgrade
wshobson
Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing. Use when upgrading framework versions, updating major dependencies, or managing breaking changes in libraries.
git-commits
bonny
Create well-structured git commits in logical chunks following best practices
git-advanced-workflows
wshobson
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
github-multi-repo
ruvnet
Multi-repository coordination, synchronization, and architecture management with AI swarm orchestration
git-workflow-enforcer
CrazyDubya
Ensures commits follow conventional commits, branch naming conventions, and PR templates. Use when creating commits, branches, or PRs, or when user mentions git workflow.