Files

T

soroush.asadi bfcd223374 M2: the four V1 atoms + Git sync (Gitea / filesystem)

- Author the four V1 skill atoms in skills/ (Git is the source of truth): spec-writing &
  story-breakdown (product-owner), test-plan-generation & diff-review (qa) — each with
  risk-tagged actions, golden tests, and a body.
- SharedKernel: IGitProvider seam (read-only, provider-agnostic) + GitFile.
- Integrations module (its first real code): FileSystemGitProvider (dogfood/local) and a
  GiteaGitProvider (Gitea REST: recursive tree → SKILL.md blobs → base64 contents); the
  provider is chosen by GitSource:Provider config.
- Skills: SkillSyncService consumes IGitProvider (never Integrations) and indexes each file;
  POST /api/skills/sync and a POST /api/skills/webhook/gitea (re-sync on push; signature
  verification + changed-file-only + queue offload come later).

Verified: build green; ArchitectureTests 8/8 (Skills & Integrations reference only
SharedKernel; the Git seam lives in SharedKernel); IntegrationTests 22/22 incl. a sync that
indexes the four real atoms from skills/, published and queryable by role.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-06-09 18:34:53 +03:30

1.5 KiB

Raw Permalink Blame History

id, name, version, summary, roles, inputs, outputs, actions, tools, context, visibility, min_tier, golden_tests

name

version

summary

roles

inputs

outputs

actions

tools

context

visibility

min_tier

golden_tests

test-plan-generation

Test Plan Generation

1.0.0

From a completed story and its diff, produce a concrete test plan.

A story (with acceptance criteria) and the diff/build that implements it.

A test plan — cases with steps and expected results, covering happy path, edges, and regressions.

name	risk	description
write-test-plan	draft	Write the test plan as a draft artifact on the QA task (held for review).

house-style

product-docs

public

free

input	expected
Story: logout button clears the session and redirects to /login. Diff: adds a header button calling signOut() then navigating to /login.	1. Happy path: signed in → click logout → session cleared, redirected to /login. 2. Edge: click logout twice quickly → no error, ends on /login. 3. Regression: protected routes redirect to /login after logout.

Test Plan Generation

You are QA. From the story's acceptance criteria and the implementing diff, write a test plan.

Cover:

Happy path — the primary success scenario for each acceptance criterion.
Edge cases — empty/invalid input, double actions, boundaries, permissions.
Regressions — nearby behaviour the diff could plausibly break.

Each case: numbered, with steps and an expected result. Keep them executable by a human or an automated test. Flag any acceptance criterion the diff does not appear to satisfy.

1.5 KiB Raw Permalink Blame History

Test Plan Generation

1.5 KiB

Raw Permalink Blame History