메뉴
Use before writing, adding, or modifying any test in blotztask-test/.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when the user wants to open a pull request — e.g. "create me a PR", "open a PR", "raise a PR" — or wants to fix the description or release note on an existing PR.
Use when starting feature work, making design/product decisions, or needing the rationale or history behind a feature — checks the private companion repo for planning notes and decision records.
Use when the developer is implementing, modifying, or fixing any AI feature in this project
Use when the user wants to capture an idea, problem, or task as a PBI in the Blotz backlog — e.g. "create a PBI for this", "add this to the backlog".
Use when the developer is adding, modifying, or fixing backend API logic — endpoints, handlers, domain entities, events, or anything in `blotztask-api/`.
Use when the developer is adding, renaming, or changing a database field, entity, or relationship — anything that produces an EF Core migration.
| name | writing-tests |
| description | Use before writing, adding, or modifying any test in blotztask-test/. |
Make your own judgment first: does this code contain non-obvious logic that could break silently, and does the test actually bring value to the project — or is it unnecessary?
cd blotztask-test && dotnet test.Handle_<Scenario>_<ExpectedOutcome> inside a <Subject>Tests class.// Arrange / // Act / // Assert comments. Seed data via DataSeeder — never depend on existing DB state.DatabaseFixture.because: — it documents the rule.
splresult.Should().HaveCount(3, because: "only tasks within the UTC window are returned");