HigorAlves/orc / codex/orc/content/skills/pr-size-budget
pr-size-budget
VerifiedUse when opening a PR or planning slices — defines the soft 300 LOC budget, the exclusion list, the shared gate prompt for ship/flow/stack-pr, and the override syntax.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.2 KB |
| references/CLI.md | markdown | 974 B |
| references/CONFIG.md | markdown | 1.2 KB |
| references/OVERRIDE-EXAMPLES.md | markdown | 709 B |
references/CONFIG.md
View on GitHub# Per-repo configuration
The optional `<repo_root>/.orc/pr-budget.json` file: migration handling and the override schema. Read this from [SKILL.md](../SKILL.md) when a repo needs a non-default budget, extra excludes, or migrations counted.
## Migrations
Migrations (`**/migrations/**/*.sql`, `prisma/migrations/**`, `db/migrate/**`) are **excluded by default**, on the theory that auto-generated migration scaffolds must not trigger the gate when the actual code change is small. Override per-repo:
```json
// <repo_root>/.orc/pr-budget.json
{
"budget": 300,
"exclude_migrations": false,
"additional_excludes": ["**/vendor/**", "docs/api-reference/**"]
}
```
If migrations are excluded, the gate prompt always **surfaces the count + LOC of excluded migration files** so the user can object if a 600-LOC migration deserves the conversation.
## Per-repo override file
Path: `<repo_root>/.orc/pr-budget.json`. Optional. Schema:
```json
{
"budget": 300,
"exclude_migrations": true,
"additional_excludes": ["glob/**", "another/glob/**"]
}
```
All keys optional. Missing keys fall through to defaults. `additional_excludes` are pathspec globs (do NOT prepend `:(exclude,glob)` — the helper does it).
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |