agf-running-sit-tests
This skill integrates with App Genesis Forge to execute system integration tests in your local environment, catching component interaction issues before they reach code review. Part of a structured 19-role development workflow that enforces quality gates at each stage, it helps ensure defects don't propagate downstream.
agf-running-sit-tests guides you through executing SIT locally in your dev environment to catch component interaction issues before code review. The skill walks you through environment setup, fixture configuration, test execution, evidence collection, and handoff preparation—ensuring defects don't propagate downstream in the App Genesis Forge workflow.
AI-generated summary based on this skill's SKILL.md
Decision gist · record as of 2026-07-19
agf-running-sit-tests guides you through executing SIT locally in your dev environment to catch component interaction issues before code review. The skill walks you through environment setup, fixture configuration, test execution, evidence collection, and handoff preparation—ensuring defects don't propagate downstream in the App Genesis Forge workflow.
Use it when
- agf-running-sit-tests covers configuring your local SIT environment using Docker Compose to spin up test fixtures and mocks.
- agf-running-sit-tests provides AC-driven walkthroughs that document SIT evidence against acceptance criteria.
Verify before relying
Read SKILL.md below before installing (1 file). Open directory: indexed for reading, not audited.
Install
pcliangx/AppGenesisForge/agf-running-sit-tests · repository language: Python
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How to run system integration tests before code review?
agf-running-sit-tests guides you through executing SIT locally in your dev environment to catch component interaction issues before code review. The skill walks you through environment setup, fixture configuration, test execution, evidence collection, and handoff preparation—ensuring defects don't propagate downstream in the App Genesis Forge workflow.
What is SIT environment setup with docker compose?
agf-running-sit-tests covers configuring your local SIT environment using Docker Compose to spin up test fixtures and mocks. This setup phase precedes test execution and ensures all backend, frontend, API, database, and external service dependencies are properly isolated and available for integration testing.
How does agf-running-sit-tests verify acceptance criteria?
agf-running-sit-tests provides AC-driven walkthroughs that document SIT evidence against acceptance criteria. You collect logs, screenshots, and test outputs to verify that components integrate correctly, then hand off results to your product lead with proof that acceptance criteria have been met before code review audit.
What are SIT preconditions and execution sequence?
agf-running-sit-tests explains SIT scope, preconditions, and the correct execution sequence for feature validation. Understanding this structure—what must be true before tests run, which tests depend on others, and how to sequence them—prevents integration test failures and ensures reliable component interaction verification.
How to collect SIT evidence and logs for handoff?
agf-running-sit-tests teaches you to gather and document SIT evidence including test logs, progress files, and actual vs. expected outputs. This evidence collection step prepares your results for product lead review and code review readiness, demonstrating that integration testing completed successfully before downstream stages.
Why is SIT dev-owned, not QA-stage testing?
agf-running-sit-tests enforces that system integration testing is a developer responsibility in the local environment, not deferred to QA. Running SIT early catches defects at the integration layer before they propagate, reducing rework and ensuring code review focuses on quality gates already validated by the developer.
SKILL.md
Rendered from the published skill. Quoted content, verbatim.
Running System Integration Tests (SIT)
Use this skill when:
- A dev finished feature code + Unit tests and is about to enter code-review
- A dev needs to verify a fix doesn't regress integration (API ↔ DB ↔ external)
What SIT is — and is not
SIT verifies that independently-developed components compose correctly — frontend ↔ backend ↔ DB ↔ external services. It is NOT:
- Unit tests (already covered by
pytest/viteston the branch before SIT) - E2E tests (real browser + real user journey — run downstream after code-review)
- UAT (business owner final sign-off — product-lead drives, downstream of E2E)
You just wrote the Unit tests, so you have the clearest picture of the unit-vs-integration boundary. If a failure reproduces by running just the backend unit tests with mocks, it's a
(truncated - see the full file via the links below)
File tree — 1 file
.claude/skills/agf-running-sit-tests/SKILL.md
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Run integration tests locally to verify components work together before code review”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
This skill automates the creation and distribution of comprehensive QA test reports within Claude Code's development environment. It captures test execution results, applies structured verdict logic, and publishes findings to stakeholders—ensuring quality gates remain enforced throughout the development lifecycle.
App Genesis Forge equips Claude Code with a structured development pipeline featuring 19 specialized roles working in concert. This skill automates simulator-based integration testing, catching composition issues before they reach code review—ensuring quality gates function like a lean manufacturing line rather than relying on a single agent.
agf-releasing-apple integrates with Claude Code to handle the final stages of iOS app delivery—taking merged main branch code and producing signed, release-ready Apple distributables. Built on App Genesis Forge's 19-role workflow model, it enforces quality gates and process discipline at each step, ensuring consistent, production-grade app releases without manual friction.
Code Review executes a systematic multi-phase examination of pull requests and code diffs, starting with scope and intent identification before conducting a critical pass for logic errors, injection vulnerabilities, and resource leaks. Specialist lenses then apply targeted checks based on change type—tests, data access, auth, or UI—with each finding assigned a confidence level to guide merge decisions.
rtk-tdd enforces the red-green-refactor cycle for Rust development, automatically guiding you through failing tests, minimal implementations, and refactoring phases. It provides Rust-idiomatic testing patterns using anyhow/thiserror, cfg(test) modules, and Arrange-Act-Assert workflows, with pre-commit gates ensuring code quality.
This skill teaches the red-green-refactor cycle: write a failing test, verify it fails for the right reason, implement just enough code to pass, then refactor. Follow the iron law—no production code without a failing test first—and use this approach for all features, bug fixes, and refactoring work.
More skills postgres-query (Apache-2.0)