Load tests
openbooklet.com/s/load-testsopenbooklet.com/s/[email protected]GET /api/v1/skills/load-testsThe harness lives in `load-tests/`. It is a standalone Maven project that compiles synthetic annotated sources with and without the processor and subtracts. `load-tests/README.md` documents the harness; `load-tests/results/README.md` documents the baselines. This skill is the judgement around both:
Paths and class names below were derived from the codebase at v1.0.0-RC3 (commits `2bc839e` Claude Code local/granular/Skill + Copilot granular, `9c61a83` AI PR-reviewers/context-packers/ Void/Roo, `406f353` Firebase AI â the smallest recent example). If a path below 404s, the architecture has dri
Paths and class names below were derived from the codebase at v1.0.0-RC3 (the `NewAnnotationsV5` wave â `@AIIdempotent`, `@AIFeatureFlag`, `@AISecure` â plus commit `df01cb8`, which fixed `BuildFingerprint` silently ignoring 12 annotation buckets and is why Step 5 below is not optional). If a pa
Bump every third-party dependency, plugin and toolchain pin in VibeTags to its latest stable release, mirror the pins Gradle cannot inherit, verify with the real gates, and open the PR. Use when the user says "bump dependencies", "update dependencies", "dependency update", "upgrade deps", "are we on the latest versions", or before a release.
Pre-push adversarial interrogation of the current branch's diff by a fresh reviewer with no memory of writing it - five scoped questions (done? production-ready? scales? secure? top risks?), answers must cite a line or admit "cannot tell from here". Advisory only, never a gate. Use when the user says "consult", "consultation loop", "are we done", "pre-push review", "interrogate this diff", or before opening a PR on substantial work.
Drives the release process documented in `docs/RELEASING.md`. That document is the source of truth; this skill is the executable path through it. If the two ever disagree, `docs/RELEASING.md` wins â and say so rather than silently improvising.
AI guardrails and coding rules generated by VibeTags from @AILocked, @AIContext, and related annotations. Load this skill when writing, reviewing, or modifying code in this project.
Auto-indexed from PIsberg/vibetags
Are you the author? Claim this skill to take ownership and manage it.
Related Skills
graceful-error-recovery
Use this skill when a tool call, command, or API request fails. Diagnose the root cause systematically before retrying or changing approach. Do not retry the same failing call without first understanding why it failed.
audience-aware-communication
Use this skill when writing any explanation, documentation, or response that will be read by someone else. Match vocabulary, depth, and format to the audience's expertise level before writing.
Refactoring Expert
Expert in systematic code refactoring, code smell detection, and structural optimization. Use PROACTIVELY when encountering duplicated code, long methods, complex conditionals, or any code quality issues. Detects code smells and applies proven refactoring techniques without changing external behavior.
Research Expert
Specialized research expert for parallel information gathering. Use for focused research tasks with clear objectives and structured output requirements.
clarify-ambiguous-requests
Use this skill when the user's request is ambiguous, under-specified, or could be interpreted in multiple ways. If proceeding with a wrong assumption would waste significant work, always ask exactly one focused clarifying question before doing anything.
structured-step-by-step-reasoning
Use this skill for any problem that involves multiple steps, tradeoffs, or non-trivial logic. Think out loud before answering to improve accuracy and transparency. Apply whenever the answer is not immediately obvious.