Files

T

Janis Eccarius 8e2afb93f3 feat: NCWF-5/6/7/8/9 chess analysis page and engine integration

- NCWF-5: scaffold /analysis route with ChessBoard viewer and navigation
- NCWF-6: FEN / PGN / Game-ID input form with depth selector
- NCWF-7: extend GameApiService with analyzePosition(); add AnalysisService
  with game-wide annotation pipeline; proxy /api/analysis -> :8087
- NCWF-8: EvalTimelineComponent — SVG win-chance chart per ply
- NCWF-9: AnnotatedMoveListComponent — quality labels (!! ! ?! ? ??)
  derived from win-chance delta

Also fix pre-existing app.spec.ts failure (missing provideHttpClient).
Apply project-wide prettier formatting pass.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

2026-06-10 15:55:14 +02:00

2.8 KiB

Raw Blame History

Create Defect in YouTrack

Automated defect creation workflow. Topic/hint: $ARGUMENTS

This is the NowChess-Frontend repo (Angular 20 / TypeScript). Defects raised here usually belong to project NCWF, but routing in Step 5 still applies.

Step 1 — Gather Context

Use AskUserQuestion tool to ask the user (max 4 questions at once):

Component — Where does the bug occur? (e.g. a component, service, route/page, model, styling, API integration)
What breaks — What is the actual (broken) behavior?
Expected — What should happen instead?
Reproducibility — Is it always reproducible? Any known trigger conditions? (route, viewport, browser)

If $ARGUMENTS already answers some of these, skip those questions.

Step 2 — Research (if needed)

If the bug involves component logic, a service, or routing:

Search repo for relevant code (Grep/Bash) under src/app/{components,services,models,core,pages}.
Check .spec.ts files for existing coverage of the broken area.
Do NOT guess at root cause. Surface findings before drafting.

Step 3 — Draft Defect

Compose the full defect report using this template:

Summary

[One-sentence description of what is broken.]


Steps to Reproduce

1. Step one
2. Step two
3. Step three


Expected Behavior

[What should happen.]


Actual Behavior

[What actually happens.]


Environment / Notes

[Any relevant context: route/URL, viewport, browser, console errors, API payloads — only if applicable.]

Rules:

Steps must be minimal and reproducible.
Expected vs actual: concrete and unambiguous.
Omit "Environment / Notes" section if not relevant.

Step 4 — Clarify

Show the draft to the user. Use AskUserQuestion tool to ask:

Are steps to reproduce complete and accurate?
Severity: Blocker / Critical / Major / Minor / Trivial?
Any related tickets or recent changes to link?

Incorporate feedback. Repeat until user approves.

Step 5 — Determine Project

Project routing rules (always apply these):

Frontend code (UI, UX, web app, components, services) → NCWF

Backend code (game engine, bots, API, services, coordinator) → NCS

Infrastructure (Kubernetes, pipelines, CI/CD, DB setup, cloud infra) → NCI

Frontend / UI / UX → project: NCWF (default for this repo)
Backend / coordinator / systems / bot / engine → project: NCS
Kubernetes, pipelines, CI/CD, infrastructure → project: NCI

If ambiguous, ask the user.

Step 6 — Create Issue

Call mcp__youtrack__create_issue with:

project: determined in Step 5
summary: concise title describing what is broken (≤72 chars, sentence case)
description: full formatted defect report from Step 3 (Markdown)
type: Bug

Step 7 — Report

Display the created issue ID and URL. Ask if a linked investigation or fix task is needed.

2.8 KiB Raw Blame History