desktop-pr-iteration

스타0

포크0

업데이트2026년 7월 9일 07:28

Open and iterate a 6529-core Electron desktop update pull request after local renderer sync and Windows build validation, including branch hygiene, PR body evidence, GitHub checks, review-bot comments, and follow-up fix commits. Use when Codex is asked to raise or shepherd a desktop update PR until CI and bots are satisfied.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

출처

6529-Collections

6529-Collections/6529-core

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Desktop PR Iteration

Carry a desktop renderer update from local validation through a normal ready-for-review PR and keep ownership until checks and review bots are satisfied.

Before Commit

Confirm the renderer sync PR uses the repository's pull-web branch when updating the bundled frontend. Do not move renderer subtree imports onto an ad hoc codex/ branch unless the repo owner explicitly asks for that.
Confirm the desktop version bump is included.
Confirm local evidence is ready: current web SHA, install result, checks, Windows build/package result, and artifact path or blocker.
Stage only intended files. A renderer subtree sync can be large; inspect the summary and any root files carefully.
Use codex-diff-check on Windows.

Commit And Push

Use a direct commit message such as:

Update desktop renderer to latest web

Push pull-web to origin. If local history contains checkpoint commits, squash or amend before push when that keeps review cleaner and does not lose useful merge metadata. Preserve subtree merge commits that record imported web history.

Pull Request

Open a normal ready-for-review PR from pull-web against main in 6529-Collections/6529-core, or update the existing open pull-web PR. Use a draft PR only when the user explicitly asks for a draft PR in the current task.

Include:

imported frontend SHA and date checked
desktop package version bump
desktop-specific conflict decisions preserved
local validation commands and results
Windows package artifact path under dist/, or the exact packaging blocker
note that publish/sign/S3 steps were not run unless explicitly requested

Bot And CI Loop

Watch GitHub checks to terminal states.
If CI fails, inspect logs before changing code. Use the GitHub CI-fix workflow or equivalent repository tooling for repeated failures.
If review bots comment, treat actionable findings as normal review feedback. Fix, test, push, and reply only with evidence.
Do not mark review threads resolved unless the fix is pushed and validated, or the finding is clearly not applicable and explained.
When coordinating in the 6529 Dev Daily Standup wave, post as punk6529bot with real 6529 mention metadata. A visible @[handle] in text is not enough; the drop payload also needs mentioned_users entries with mentioned_profile_id and handle_in_content.
The 6529bot responsiveness harness runs the repository root ./bin/6529 run dev on Ubuntu and expects the renderer web app at PORT=3001. Preserve the narrow bot-server branch in bin/6529 that delegates this path to renderer/; it detects either REVIEWBOT_RESPONSIVENESS_OUTPUT_DIR or the generated Playwright server env (PORT_SEARCH_LIMIT=1, localhost BASE_ENDPOINT, prod API/WS endpoints, ASSETS_FROM_S3=true). That branch must run root build-next-config before entering renderer/, so Next loads the generated root next.config.mjs instead of trying to compile next.config.ts during the bot dev server start. The normal desktop dev path should still start Electron.
CodeQL may flag imported renderer media sinks after a web pull. Keep URL handling real, not cosmetic: sanitize audio/video source URLs through an allowlist before assigning src, remove unnecessary clickable links for untrusted iframe banners, and route server-side preview fetches through fetchPublicUrl instead of raw fetch when the request URL depends on preview metadata or user-submitted URLs. Inline CodeQL suppressions may not be honored by the PR gate, so prefer a guard path that the scanner can see or an explicit repository-level security decision.
Stop after CI and bots are happy. Do not merge unless the user explicitly asks to merge.

Closeout

Report PR URL, head SHA, web SHA imported, local build/package evidence, CI/review status, and remaining risks.

이 저장소의 다른 Skills

같은 저장소

6529-autonomous-manager

6529-Collections/6529-core

Own scoped 6529 frontend workstreams end to end. Use when Codex is asked to act as a manager, workstream owner, PR owner, review-feedback owner, release/staging/prod coordinator, ops/skills package owner, or autonomous implementation lead for the 6529seize frontend repository.

2026-07-060

deploy-6529

6529-Collections/6529-core

Merge and deploy 6529 frontend or coordinated frontend/backend releases through staging and production with explicit approval gates, GitHub Actions or repo-approved deploy paths, staging and production E2E/smoke validation, autonomous failed-gate recovery, rollback or fix-forward handling, and coordination with other active Codex agents. Use when Codex is asked to merge PRs, deploy to staging, validate staging, promote to production, validate production, recover from failed deploy/E2E, or coordinate a 6529seize-backend deployment with frontend release work.

2026-07-060

sync-desktop-renderer

6529-Collections/6529-core

Sync the 6529 web frontend into the 6529-core Electron renderer subtree, preserve desktop-only behavior, resolve pull-web conflicts, update duplicated desktop config, and bump the desktop version. Use when Codex is asked to bring the Electron desktop app up to date with recent or current 6529.io frontend changes.

2026-07-010

write-prs

6529-Collections/6529-core

Write, open, iterate, and prepare pull requests for merge or deployment with clear PR descriptions, safe validation notes, review-bot follow-up, signed commits, readiness gates, and deployment handoff notes. Use when preparing PR bodies, creating PRs, responding to CodeRabbit or Claude review bots, deciding whether a PR is ready, or preparing a PR for merge, staging, or production rollout; use deploy-6529 for actual deployment execution.

2026-06-190

test-desktop-build

6529-Collections/6529-core

Validate a 6529-core Electron desktop update on Windows with secure installs, renderer and Electron type/build checks, local package creation, artifact inspection, and Windows-specific environment constraints. Use when Codex needs to test or package the 6529 Electron app before a PR or release.

2026-06-180

name	desktop-pr-iteration
description	Open and iterate a 6529-core Electron desktop update pull request after local renderer sync and Windows build validation, including branch hygiene, PR body evidence, GitHub checks, review-bot comments, and follow-up fix commits. Use when Codex is asked to raise or shepherd a desktop update PR until CI and bots are satisfied.

Desktop PR Iteration

Carry a desktop renderer update from local validation through a normal ready-for-review PR and keep ownership until checks and review bots are satisfied.

Before Commit

Confirm the renderer sync PR uses the repository's pull-web branch when updating the bundled frontend. Do not move renderer subtree imports onto an ad hoc codex/ branch unless the repo owner explicitly asks for that.
Confirm the desktop version bump is included.
Confirm local evidence is ready: current web SHA, install result, checks, Windows build/package result, and artifact path or blocker.
Stage only intended files. A renderer subtree sync can be large; inspect the summary and any root files carefully.
Use codex-diff-check on Windows.

Commit And Push

Use a direct commit message such as:

Update desktop renderer to latest web

Pull Request

Include:

imported frontend SHA and date checked
desktop package version bump
desktop-specific conflict decisions preserved
local validation commands and results
Windows package artifact path under dist/, or the exact packaging blocker
note that publish/sign/S3 steps were not run unless explicitly requested

Bot And CI Loop

Watch GitHub checks to terminal states.
If CI fails, inspect logs before changing code. Use the GitHub CI-fix workflow or equivalent repository tooling for repeated failures.
If review bots comment, treat actionable findings as normal review feedback. Fix, test, push, and reply only with evidence.
Do not mark review threads resolved unless the fix is pushed and validated, or the finding is clearly not applicable and explained.
When coordinating in the 6529 Dev Daily Standup wave, post as punk6529bot with real 6529 mention metadata. A visible @[handle] in text is not enough; the drop payload also needs mentioned_users entries with mentioned_profile_id and handle_in_content.
The 6529bot responsiveness harness runs the repository root ./bin/6529 run dev on Ubuntu and expects the renderer web app at PORT=3001. Preserve the narrow bot-server branch in bin/6529 that delegates this path to renderer/; it detects either REVIEWBOT_RESPONSIVENESS_OUTPUT_DIR or the generated Playwright server env (PORT_SEARCH_LIMIT=1, localhost BASE_ENDPOINT, prod API/WS endpoints, ASSETS_FROM_S3=true). That branch must run root build-next-config before entering renderer/, so Next loads the generated root next.config.mjs instead of trying to compile next.config.ts during the bot dev server start. The normal desktop dev path should still start Electron.
CodeQL may flag imported renderer media sinks after a web pull. Keep URL handling real, not cosmetic: sanitize audio/video source URLs through an allowlist before assigning src, remove unnecessary clickable links for untrusted iframe banners, and route server-side preview fetches through fetchPublicUrl instead of raw fetch when the request URL depends on preview metadata or user-submitted URLs. Inline CodeQL suppressions may not be honored by the PR gate, so prefer a guard path that the scanner can see or an explicit repository-level security decision.
Stop after CI and bots are happy. Do not merge unless the user explicitly asks to merge.

Closeout

Report PR URL, head SHA, web SHA imported, local build/package evidence, CI/review status, and remaining risks.