You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Chore: Frontend Quality Refactor & Test Suite DRY-ing (#8)
* chore(docs): update devops-agent.md to include CI/CD workflow review and deployment roadmap
* chore(fe): replace window with globalThis for better compatibility
* chore(docker): update production image to use specific SHA for consistency
* chore(tests): improve credential verification in BFF integration tests to avoid dead stores variables requestMadeWithCredentials
* feat(agent): add git-worktree-manager skill
Adds a new agent skill for managing git worktrees safely. This enables parallel development workflows by allowing the agent to create, manage, and remove sibling worktrees for isolated tasks.
* refactor(frontend): use Readonly type for AuthProvider props
Updates the AuthProvider component to use Readonly<AuthProviderProps>. This enforces immutability for the component props, aligning with React best practices and improving type safety.
description: Manages the lifecycle of Git worktrees for parallel development tasks. Handles creation, safe removal, and branch management to keep the main working directory clean.
4
+
---
5
+
6
+
# Git Worktree Manager Skill
7
+
8
+
This skill enables the agent to safely create, manage, and destroy Git worktrees. This allows for parallel development (e.g., fixing a bug while in the middle of a feature) without disrupting the main working directory.
9
+
10
+
## 1. Directory Strategy
11
+
To prevent path resolution issues and nesting conflicts, all worktrees MUST be created as **siblings** to the current project root.
12
+
13
+
***Current Root**: `../project-name`
14
+
***Worktree Root**: `../project-name-<feature>`
15
+
16
+
**Example:**
17
+
If working in `P:/dev/my-app`, a worktree for a "auth-fix" should be at `P:/dev/my-app-auth-fix`.
18
+
19
+
## 2. Worktree Protocols
20
+
21
+
### <PROTOCOL:WORKTREE_CREATE>
22
+
**Trigger**: When the user needs to switch contexts (e.g., "fix this bug" while changes are unstaged) or explicitly requests a clean environment.
23
+
24
+
1.**Analyze Request**: Determine the target branch name and the purpose.
25
+
2.**Determine Path**: Construct the sibling path `../<current_folder_name>-<short-description>`.
4.**Confirm**: Report the location of the new worktree and remind the user that dependencies (like `node_modules`) may need to be re-installed there.
30
+
31
+
### <PROTOCOL:WORKTREE_REMOVE>
32
+
**Trigger**: When the task in the worktree is complete and changes are committed.
33
+
34
+
1.**Verify State**: Ensure changes in the worktree are committed or stashable.
35
+
2.**Execute Removal**:
36
+
* Attempt standard removal: `git worktree remove <path>`
37
+
**Handle Untracked Files*: If the command fails because of untracked files (e.g., `node_modules`, `target/`), and the work is definitely saved/committed, use force: `git worktree remove --force <path>`.
38
+
3.**Prune**: Run `git worktree prune` to clean up references.
39
+
40
+
## 3. Operational Guidelines
41
+
42
+
***Dependency Awareness**: A new worktree is a fresh checkout. It does **not** share `node_modules`, `target`, or `venv` folders. You MUST check for their existence and run install commands (`npm install`, `./mvnw compile`) before running tests in the new worktree.
43
+
***Path Context**: When operating in a worktree, always use absolute paths or relative paths carefully calculated from the worktree root.
44
+
***Shell Context**: When running shell commands, explicitly `cd` into the worktree directory: `cd ../<worktree-path>; <command>`.
Copy file name to clipboardExpand all lines: website/docs/agent/prompts/devops-agent.md
+10-8Lines changed: 10 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,8 +21,18 @@ Analyze
21
21
-`*.config` in the frontend
22
22
- all nginx files (incl for the ./webiste) are configured correctly
23
23
-`template-realm.json` for Keycloak setup and user creation
24
+
- all `.github/workflows/*.yml` for CI/CD pipelines
24
25
25
26
We need to make sure every variable is injected properly and all ports, hostnames are set up properly.
27
+
I need a clear roadmap to move from local development to a infomaniak jelastic deployment. What do i need to implement ? configure etc... to be able to create then a complete CI/CD pipeline to deploy the app to jelastic from github actions.
28
+
29
+
# Output Format
30
+
Please provide the review in this Markdown format:
3.**Network & SSL Config:** (e.gProxy settings for OAuth2).
34
+
4.**Ready-to-Deploy Fixes:** specific code blocks to update `compose.yaml` or `Dockerfile`.
35
+
5.**Manual tests procedure on local docker-compose:** (e.g curl commands to verify service connectivity).
26
36
27
37
## 1. Jelastic & Docker Compatibility (Critical)
28
38
***Base Images:** Verify we are using valid, public Docker Hub images for Java 25 (e.g., `eclipse-temurin:25` or `openjdk:25-slim`). Jelastic requires the image to be pullable from a registry if not built locally.
@@ -51,11 +61,3 @@ We need to make sure every variable is injected properly and all ports, hostname
51
61
## 4. Compose to Jelastic Translation
52
62
***Volume Mounts:** Check for local volume binds (e.g., `./config:/app/config`). These will break on Jelastic unless you are using specific "Add-on" storage configurations. Suggest converting these to Environment Variables or ConfigMaps where possible.
53
63
***Restart Policy:** Ensure `restart: always` or `unless-stopped` is defined.
54
-
55
-
# Output Format
56
-
Please provide the review in this Markdown format:
Copy file name to clipboardExpand all lines: website/docs/agent/prompts/fe-agent.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
# Role & Objective
2
-
Act as a Senior Frontend Security Architect specialized in React 19, TypeScript 5.9, and OpenAPI-driven development. Your goal is to perform a security and code review of the React frontend.
2
+
Act as a Senior Frontend Developer specialized in React 19, TypeScript 5.9, and OpenAPI-driven development. Your goal is to perform a security and code review of the React frontend.
0 commit comments