test-codebase
Run or inspect the relevant validation paths and turn failures, regressions, or missing coverage into findings. Accept optional `path` and `depth` parameters and default to `path=infer`, `depth=deep`. Confirm effective variables before starting.
git clone --depth 1 https://github.com/Agenta-AI/agenta /tmp/test-codebase && cp -r /tmp/test-codebase/.agents/skills/test-codebase ~/.claude/skills/test-codebaseSKILL.md
# Test Codebase Read these shared references when needed: - `../shared/references/findings.schema.md` - `../shared/references/findings.lifecycle.md` ## Role Run validation-oriented testing work and convert the result into findings. - Use existing tests, targeted repro steps, docs, and runtime behavior. - Prefer the smallest test or repro surface that can validate the suspected behavior. - If the environment prevents execution, record that limitation explicitly and turn the blocked validation gap into a finding instead of pretending the test ran. ## Depth Accept a `depth` parameter from the prompt: - `shallow` - `deep` Default: - `depth=deep` ## Path Input Accept an optional `path` from the prompt. - If `path` is provided, use it as the local design or findings folder. - If `path` is omitted, infer it from the branch, subsystem, or matching docs and state the inferred value before starting. Default: - `path=infer` ## Workflow 1. Establish validation scope. Confirm the effective variables first: - `path` - `depth` - relevant test environment or constraints - branch, subsystem, and any requested focus areas 2. Choose the validation surface. Use existing tests first when they are relevant. Add targeted repro or smoke execution when that is the shortest way to validate behavior. 3. Run or inspect. Execute the chosen tests or repro steps when possible. If execution is blocked, record the blocker and its impact explicitly. 4. Turn outcomes into findings. Capture broken behavior, flaky behavior, missing coverage, missing assertions, environment gaps, and rollout risks in the active findings record. 5. Update the active findings record. Use `path/findings.md`. 6. Hand off when review or implementation is needed. Use `triage-findings` for follow-up questions and planning. Use `resolve-findings` when the intended fix path is clear. ## Rules - This skill is validation-oriented. - Do not treat static code reading as test execution. - Do not overrun the whole suite when a narrow validation pass is enough.
Helps add announcement cards to the sidebar banner system. Use when adding changelog entries, feature announcements, updates, or promotional banners to the Agenta sidebar. Handles both simple changelog entries and complex custom banners.
Playbook for adding a new coding-agent harness to Agenta (Codex, Hermes, Gemini, OpenCode, ...). Use when starting, planning, or reviewing a new-harness project. Covers the readiness audit of prior art, the spike-first milestone plan, the full integration-surface checklist, the per-harness variance axes to probe, and the process/communication contract with Mahmoud. Living document: every harness project appends its lessons to resources/LESSONS.md.
>-
Where to put frontend code (package vs app layer) and how to use the @agenta/* packages. Use when authoring or moving code in web/packages, choosing between @agenta/ui, @agenta/entities, @agenta/entity-ui, @agenta/shared, @agenta/playground, using molecules, loadable/runnable bridges, the EntityPicker, or writing package unit tests.
Use this skill to create and publish changelog announcements for new features, improvements, or bug fixes. This skill handles the complete workflow - creating detailed changelog documentation pages, adding sidebar announcement cards, and ensuring everything follows project standards. Use when the user mentions adding changelog entries, documenting new features, creating release notes, or announcing product updates.
Hard-won GitButler mechanics for multi-lane work in this repo — committing to a specific lane in a stack, spreading a pile of edits back across an existing stack, ordering a stack and setting PR bases, and recovering from a scrambled workspace. Use when working with stacked branches, when `but rub`/`but absorb`/`but commit --only` mis-routes a change, when a stack collapses or a commit lands on the wrong lane, or when a hunk gets dropped. Not needed for ordinary single-lane work.
Drive a researched and planned feature to a landed, tested change. Use after plan-feature has produced a docs/design/<project>/ workspace and the user says "implement it", "build the plan", "run the plan", or "let's ship this". Orchestrates refresh-plan, implement, review, a debug-local-deployment loop, and a test loop across the daytona / local-pi / claude x SDK / UI matrix, then documentation and a GitButler stacked branch. The orchestrator stays in the loop and spins narrow subagents for each phase.
Feature-folder layout, states/ convention, and data-flow rules for the Agenta mobile app (web/mobile). Use when creating or moving files under web/mobile, deciding where a component lives, adding a new feature or screen, or wiring data into mobile components.