developer-pre-pr-checklist

Validates Axentra code changes against required checks before opening pull requests.

Updated Sep 16, 2026
One-click install
npx skills add https://github.com/PT-Perkasa-Pilar-Utama/axentra --skill developer-pre-pr-checklist-pt-perkasa-pilar-utama
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: developer-pre-pr-checklist
Source: https://github.com/PT-Perkasa-Pilar-Utama/axentra/tree/main/.claude/skills/developer-pre-pr-checklist
Command: npx skills add https://github.com/PT-Perkasa-Pilar-Utama/axentra --skill developer-pre-pr-checklist-pt-perkasa-pilar-utama

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Developers risk opening pull requests that fail CI, leak credentials, or skip required verification steps. This Skill enforces the Axentra pre-PR checklist so every change passes formatting, lint, type-check, tests, and builds before review. ## Core Features & Use Cases - Required Verification: Runs bun run complete-check from the repository root to execute formatting, lint, type-check, tests, and builds for the web, API, and worker. - Self-Review Checklist: Confirms task IDs and acceptance criteria are in the PR, diffs are scoped without secrets or build output, and server-side authorization and error envelopes are enforced. - Branching Discipline: Ensures work targets the dev branch via a feature branch PR, never pushing directly to protected dev or main. - Use Case: Before requesting review from Tech Lead Arya Isnaidi, a developer uses this Skill to verify CI checks are green and the docs/TASK_BREAKDOWN.md card is marked In Review. ## Quick Start Ask the assistant to run the pre-PR checklist on my current Axentra feature branch before I open a pull request into dev.

Frequently Asked Questions about developer-pre-pr-checklist

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify changes before opening a pull request in Axentra?▼

Run bun run complete-check from the repository root to execute formatting, lint, type-check, tests, and builds for the web, API, and worker. Then complete the self-review checklist covering scoped diffs, acceptance criteria, and green CI.

What checks does bun run complete-check include?▼

It runs formatting, lint, type-check, tests, and builds across the web, API, and worker processes. For database changes, you must also run the disposable Postgres migration check described in docs/CODING_STANDARD.md.

Can I push directly to the dev or main branch in Axentra?▼

No, dev and main are protected branches. Push only your feature branch and open a pull request into dev; main is release-only and the Tech Lead Arya Isnaidi is the final reviewer.

What should a pull request include before requesting review?▼

Include the task ID and acceptance criteria, keep the diff scoped without generated output or credentials, mark the docs/TASK_BREAKDOWN.md card as In Review, and confirm CI checks are green.

Why did my Axentra PR get rejected during review?▼

Common causes include unscoped diffs with build output or env files, missing server-side authorization or error envelopes, UI tested with static data instead of persistence, or skipped migration protocol for database changes.