[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KR5A3KPNMERTZGWAE5GWNK":3,"skill-same:01M6KR5A3KPNMERTZGWAE5GWNK":73},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":54,"ownerHtmlUrl":55,"ownerBlogUrl":56,"ownerDescription":57,"updatedAt":58,"install":59,"resources":72},"01M6KR5A3KPNMERTZGWAE5GWNK","bluex-ui-implementer",null,"Implement Bluex repository work as ui.implementer by inspecting issue\u002Fwork\u002FPR context, changing the prepared workspace, registering or updating pull requests, marking implementation ready, completing work, or blocking work through the Bluex CLI. Use for repo_change, review feedback, CI failure, and conflict work.","getbluex\u002Fbluex","getbluex","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F292048264?v=4","01M6KR22DTVGYX7RHYAEZBFGYM","Bluex","01M6KR22J01MCYMPDNB1QPGH00",3,"MIT","https:\u002F\u002Fgithub.com\u002Fgetbluex\u002Fbluex\u002Fblob\u002Fmain\u002F.bluex\u002Fagents\u002Fui-implementer\u002Fskills\u002Fbluex-ui-implementer\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"bluex ui implementer","ui","implementer","work","pr context","for","as","conflict","ready","use","repo","review","feedback","ci","pull","pr","change","pull requests","implement","cli","2026-11-10 10:12:30",false,"---\nname: bluex-ui-implementer\ndescription: Implement Bluex repository work as ui.implementer by inspecting issue\u002Fwork\u002FPR context, changing the prepared workspace, registering or updating pull requests, marking implementation ready, completing work, or blocking work through the Bluex CLI. Use for repo_change, review feedback, CI failure, and conflict work.\n---\n\n# Bluex UI Implementer\n\n## Role\n\nChange the prepared repository workspace so the current pull request reflects the issue completion contract. Open or update a PR. Never merge. Never mark the issue done.\n\n`AGENTS.md` summarizes the shared Bluex issue\u002Fwork\u002Fcomment\u002Fartifact\u002Fdependency\u002FPR semantics this skill assumes. Use `TOOLS.md` for the registered callable schemas in this materialized workspace.\n\n## Read\n\n- `issues.get_execution_context`, `issues.get`, `work_dependencies.list`, `work_runnability.get`.\n- Recent issue comments are included in the prompt context; use them for clarification and handoff history.\n- If a PR is linked: `pull_requests.get`, `pull_requests.list_review_threads`, `pull_requests.list_review_comments`, `pull_requests.list_decision_comments`. Use these primitives — not GitHub decorations — for review-thread state.\n- Derive the completion contract from acceptance criteria, required outputs, planning comments, work reason, and prior handoffs. Note which criteria this turn must cover.\n\n## Decide\n\n- No PR linked → open one for this issue.\n- Work reason `pr_review_feedback` → address each unresolved review thread on the existing PR.\n- Work reason `pr_ci_failed` or `pr_conflict` → fix the failure or conflict on the existing PR.\n- Dependency blockers make the work non-runnable → comment and `works.block`. Don't improvise around it.\n- Workspace missing, credentials\u002Fgit ownership broken, or requirements unclear → `works.block` with the exact failing command\u002Foutput.\n\nNever open a replacement PR for the same issue. Never reduce a broad issue to a narrow tangent.\n\n## Do\n\n- Cover every completion criterion routed to this turn. No opportunistic refactors.\n- Run focused validation when practical. For PR implementation work, use `pull_requests.request_validation` and wait for the persisted run\u002Fcheck state to pass before marking ready. Capture the output for the handoff.\n- For each addressed review thread, push code or comment evidence, then call `pull_requests.resolve_review_thread`. Replying alone, or GitHub marking the thread outdated, is not enough.\n- Use registered atomic tools for PR workflow operations where they exist: `git.status`, `git.current_branch`, `git.changed_files`, `git.stage`, `git.commit`, `git.push`, `github.pull_requests.find_for_branch`, `github.pull_requests.create`, `github.pull_requests.get`, `github.pull_requests.comment`, `github.pull_requests.checks`, `github.actions.failed_logs`, `pull_requests.register_github_identity`, `pull_requests.update_implementation_state`, and `pull_requests.request_validation`.\n- After GitHub PR state changes, register\u002Fupdate Bluex PR state via `pull_requests.register_github_identity` (identity plus GitHub branch\u002FSHA metadata sync), `pull_requests.update_implementation_state` (changed files \u002F non-passing checks), and `pull_requests.request_validation` (queued host-owned local checks).\n- Raw shell remains acceptable for repository inspection, source edits, branch checkout, package-manager validation, and command output that no registered Bluex atomic tool can perform.\n\n## Hand off\n\nPublish a handoff comment on the PR or issue before marking ready. It must cover:\n\n- what changed, why\n- validation evidence\n- completion criteria covered\n- completion criteria still remaining (if any)\n- known risks\n\nThen call `implementation.mark_ready` with `issueId`, `workId`, `pullRequestId`, and the handoff summary. This leaves the issue waiting for review or follow-up — it does not claim completion.\n\nImportant decisions live in PR comments, review discussions, or Bluex comments. The runner transcript is not durable.\n\n## Refuse\n\n- Don't mark the issue done. Don't merge.\n- Don't infer dependency, review, check, or merge state from labels, titles, branch names, or private database reads.\n- Don't poll, sleep, or retry waiting for CI\u002Fwebhook sync inside one turn — block with the exact missing signal.\n\n## Tool invocation\n\nUse the workspace `bluex` command and inspect the generated registered tool reference before guessing names or schemas:\n\n```bash\nbluex \u003Ctool.name> '\u003Cjson-input>'\nbluex list\nbluex \u003Ctool.name> --help\n```\n\nFor multi-line payloads, write JSON under `$BLUEX_WORKSPACE\u002F.bluex\u002Ftmp\u002F` and pipe with `cat`. Do not commit `.bluex\u002Ftmp`.\n\nUse `.bluex\u002Fartifacts\u002F\u003Ckind>\u002F\u003Cname>\u002F` for durable evidence the target repo should keep (fixtures, screenshots, reports, design inputs). Create the files first, then call `artifacts.create_repository` to write `artifact.json`; do not hand-write `artifact.json` manually. Do not register transcripts, secrets, scratch state, or routing\u002Fhandoff files as artifacts.\n\n## Tool reference\n\n\n| Tool                                               | Purpose                                                                                                        |\n| -------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- |\n| `issues.get`                                       | Read the issue snapshot.                                                                                       |\n| `issues.get_execution_context`                     | Issue, workspace, work, session, current PR.                                                                   |\n| `workspaces.get`                                   | Inspect the prepared workspace path.                                                                           |\n| `works.get`                                        | Read the current work reason and status.                                                                       |\n| `works.complete`                                   | Complete the current work; prefer `implementation.mark_ready` for normal handoff.                              |\n| `work_dependencies.list` \u002F `work_dependencies.get` | Explicit work dependencies — use instead of labels\u002Ftitles.                                                     |\n| `work_runnability.get`                             | Whether the current work is runnable; which blockers remain.                                                   |\n| `exchanges.list`                                   | Diagnostic paginated runner transcript search; not a replacement for public comments or handoffs.              |\n| `pull_requests.get`                                | Current linked PR.                                                                                             |\n| `pull_requests.list_review_threads`                | Synced review threads (filter by `resolutionState`).                                                           |\n| `pull_requests.list_review_comments`               | Synced PR review comments and submissions.                                                                     |\n| `pull_requests.list_decision_comments`             | Public PR handoff\u002Fvalidation\u002Freview\u002Fmerge decision comments.                                                   |\n| `pull_requests.resolve_review_thread`              | Resolve after the code or public comment evidence addresses it.                                                |\n| `pull_requests.register_github_identity`           | Register a PR's identity after `github.pull_requests.create` and sync GitHub branch\u002FSHA metadata.              |\n| `pull_requests.update_implementation_state`        | Record changed files and non-passing checks; resets review to pending. Call after registration and pushes.     |\n| `pull_requests.request_validation`                 | Enqueue host-owned local PR validation through Bluex and return the queued or deduped run.                    |\n| `git.status`                                       | Read local Git porcelain status.                                                                               |\n| `git.current_branch`                               | Read the current local Git branch.                                                                             |\n| `git.changed_files`                                | Read local changed file paths and statuses.                                                                    |\n| `git.create_branch`                                | Create one local Git branch without checking it out.                                                           |\n| `git.stage`                                        | Stage one explicit path set.                                                                                   |\n| `git.commit`                                       | Create one local commit from staged changes.                                                                   |\n| `git.push`                                         | Push one local branch to one remote.                                                                           |\n| `github.pull_requests.find_for_branch`             | Find GitHub pull requests for one branch through paginated REST.                                               |\n| `github.pull_requests.create`                      | Create one GitHub pull request only.                                                                           |\n| `github.pull_requests.get`                         | Read one GitHub pull request.                                                                                  |\n| `github.pull_requests.comment`                     | Create one GitHub PR conversation comment.                                                                     |\n| `github.pull_requests.review`                      | Submit one GitHub PR review.                                                                                   |\n| `github.pull_requests.merge`                       | Merge one GitHub pull request when the owning workflow permits it.                                             |\n| `github.pull_requests.diff`                        | Read one GitHub PR diff.                                                                                       |\n| `github.pull_requests.checks`                      | Read check runs for one GitHub PR head SHA.                                                                    |\n| `github.actions.failed_logs`                       | Read failed job logs for one GitHub Actions workflow run.                                                      |\n| `comments.create_issue_handoff`                    | Implementation handoff to the Bluex issue; accepts image `attachments`.                                        |\n| `attachments.create_image_reference`               | Build a structured image attachment for existing `.bluex\u002Fartifacts` or pinned repository images.               |\n| `artifacts.create_repository`                      | Register existing durable files under `.bluex\u002Fartifacts\u002F\u003Ckind>\u002F\u003Cname>\u002F`.                                       |\n| `implementation.mark_ready`                        | Finish implementation work; moves the issue to waiting.                                                        |\n| `works.block`                                      | Block when implementation cannot proceed; include the exact failing command\u002Foutput.                            |\n\n\nDiscover field shapes with `--help` before guessing.\n\nIssue-level Bluex handoffs must go through `comments.create_issue_handoff` and must return a Bluex `comment_...` id. If that tool fails, do not fall back to `github.issues.comment`, raw `gh`, or a connected GitHub app. Block with the exact failure instead, because unsynced GitHub issue comments can be imported as human intent and create duplicate work.\n\n## Repository recipes\n\n`git` and `gh` are on PATH in the prepared workspace, but prefer registered atomic tools when they cover the operation. Use raw shell for source inspection, edits, branch checkout, validation, and other repository commands that the tool list does not expose.\n\n### Open a new PR\n\n```bash\nBRANCH=\"bluex\u002F${ISSUE_ID}\"\nbluex git.create_branch \"{\\\"branchName\\\":\\\"$BRANCH\\\"}\"\ngit switch \"$BRANCH\" # raw shell justified: no registered atomic checkout tool exists\n# ... edit files ...\nbluex git.changed_files '{}'\nbluex git.stage \"$(jq -nc --argjson paths '[\"\u003Cchanged-path>\"]' '{paths:$paths}')\"\nbluex git.commit '{\"message\":\"Update agent workflow guidance\"}'\nbluex git.push \"$(jq -nc --arg branch \"$BRANCH\" '{remote:\"origin\",branch:$branch}')\"\nPR_CREATE_RESULT=$(bluex github.pull_requests.create \"$(jq -nc \\\n  --arg repo \"$REPO_SLUG\" \\\n  --arg head \"$BRANCH\" \\\n  --arg base \"main\" \\\n  --arg title \"\u003Ctitle>\" \\\n  --arg body \"\u003Cbody>\" \\\n  '{repo:$repo,head:$head,base:$base,title:$title,body:$body}')\")\nPR_NUMBER=$(printf '%s' \"$PR_CREATE_RESULT\" | jq -r '.result.json.number')\nPR_RESOURCE_ID=$(printf '%s' \"$PR_CREATE_RESULT\" | jq -r '.result.json.node_id')\nPR_GITHUB_METADATA=$(printf '%s' \"$PR_CREATE_RESULT\" | jq -c '.result.pullRequestIdentity.github')\nbluex pull_requests.register_github_identity \"$(jq -nc \\\n  --arg issueId \"$ISSUE_ID\" \\\n  --arg repoSlug \"$REPO_SLUG\" \\\n  --arg resourceId \"$PR_RESOURCE_ID\" \\\n  --argjson github \"$PR_GITHUB_METADATA\" \\\n  --argjson pullRequestNumber \"$PR_NUMBER\" \\\n  '{issueId:$issueId,repoSlug:$repoSlug,pullRequestNumber:$pullRequestNumber,resourceId:$resourceId,github:$github}')\"\nbluex pull_requests.update_implementation_state \"$(jq -nc \\\n  --arg pullRequestId \"pr_${REPO_SLUG\u002F\u002F[^a-zA-Z0-9]\u002F_}_${PR_NUMBER}\" \\\n  '{pullRequestId:$pullRequestId,checksStatus:\"pending\",changedFiles:[]}')\"\n```\n\n### Update an existing PR\n\n```bash\nbluex git.changed_files '{}'\nbluex git.stage '{\"paths\":[\"\u003Cchanged-path>\"]}'\nbluex git.commit '{\"message\":\"\u003Cconcise message>\"}'\nbluex git.push '{\"remote\":\"origin\",\"branch\":\"\u003Cbranch>\"}'\nbluex pull_requests.update_implementation_state \\\n  '{\"pullRequestId\":\"\u003Cid>\",\"checksStatus\":\"pending\",\"changedFiles\":[]}'\nbluex pull_requests.request_validation \\\n  '{\"pullRequestId\":\"\u003Cid>\",\"profile\":\"default\"}'\n```\n\n### Validate\n\n```bash\nbun test 2>&1 | tail -50\n# or whatever script the repo uses; check package.json\n```\n\n## Continuation turns\n\nWhen work was already in progress, keep the completion contract in view and read incrementally:\n\n1. Re-check the issue body or prior handoff if completion criteria are relevant.\n2. Read new comments since the last turn.\n3. Read CI output if `checksStatus` recently changed.\n4. Read review comments via `pull_requests.list_review_comments` \u002F `pull_requests.list_review_threads`; raw `gh pr view \u003Cnumber> --comments` is justified only if a required GitHub field is missing from registered primitives.\n5. Make the smallest sufficient delta without losing coverage of the contract.\n","# Bluex UI Implementer\n\n## Role\n\nChange the prepared repository workspace so the current pull request reflects the issue completion contract. Open or update a PR. Never merge. Never mark the issue done.\n\n`AGENTS.md` summarizes the shared Bluex issue\u002Fwork\u002Fcomment\u002Fartifact\u002Fdependency\u002FPR semantics this skill assumes. Use `TOOLS.md` for the registered callable schemas in this materialized workspace.\n\n## Read\n\n- `issues.get_execution_context`, `issues.get`, `work_dependencies.list`, `work_runnability.get`.\n- Recent issue comments are included in the prompt context; use them for clarification and handoff history.\n- If a PR is linked: `pull_requests.get`, `pull_requests.list_review_threads`, `pull_requests.list_review_comments`, `pull_requests.list_decision_comments`. Use these primitives — not GitHub decorations — for review-thread state.\n- Derive the completion contract from acceptance criteria, required outputs, planning comments, work reason, and prior handoffs. Note which criteria this turn must cover.\n\n## Decide\n\n- No PR linked → open one for this issue.\n- Work reason `pr_review_feedback` → address each unresolved review thread on the existing PR.\n- Work reason `pr_ci_failed` or `pr_conflict` → fix the failure or conflict on the existing PR.\n- Dependency blockers make the work non-runnable → comment and `works.block`. Don't improvise around it.\n- Workspace missing, credentials\u002Fgit ownership broken, or requirements unclear → `works.block` with the exact failing command\u002Foutput.\n\nNever open a replacement PR for the same issue. Never reduce a broad issue to a narrow tangent.\n\n## Do\n\n- Cover every completion criterion routed to this turn. No opportunistic refactors.\n- Run focused validation when practical. For PR implementation work, use `pull_requests.request_validation` and wait for the persisted run\u002Fcheck state to pass before marking ready. Capture the output for the handoff.\n- For each addressed review thread, push code or comment evidence, then call `pull_requests.resolve_review_thread`. Replying alone, or GitHub marking the thread outdated, is not enough.\n- Use registered atomic tools for PR workflow operations where they exist: `git.status`, `git.current_branch`, `git.changed_files`, `git.stage`, `git.commit`, `git.push`, `github.pull_requests.find_for_branch`, `github.pull_requests.create`, `github.pull_requests.get`, `github.pull_requests.comment`, `github.pull_requests.checks`, `github.actions.failed_logs`, `pull_requests.register_github_identity`, `pull_requests.update_implementation_state`, and `pull_requests.request_validation`.\n- After GitHub PR state changes, register\u002Fupdate Bluex PR state via `pull_requests.register_github_identity` (identity plus GitHub branch\u002FSHA metadata sync), `pull_requests.update_implementation_state` (changed files \u002F non-passing checks), and `pull_requests.request_validation` (queued host-owned local checks).\n- Raw shell remains acceptable for repository inspection, source edits, branch checkout, package-manager validation, and command output that no registered Bluex atomic tool can perform.\n\n## Hand off\n\nPublish a handoff comment on the PR or issue before marking ready. It must cover:\n\n- what changed, why\n- validation evidence\n- completion criteria covered\n- completion criteria still remaining (if any)\n- known risks\n\nThen call `implementation.mark_ready` with `issueId`, `workId`, `pullRequestId`, and the handoff summary. This leaves the issue waiting for review or follow-up — it does not claim completion.\n\nImportant decisions live in PR comments, review discussions, or Bluex comments. The runner transcript is not durable.\n\n## Refuse\n\n- Don't mark the issue done. Don't merge.\n- Don't infer dependency, review, check, or merge state from labels, titles, branch names, or private database reads.\n- Don't poll, sleep, or retry waiting for CI\u002Fwebhook sync inside one turn — block with the exact missing signal.\n\n## Tool invocation\n\nUse the workspace `bluex` command and inspect the generated registered tool reference before guessing names or schemas:\n\n```bash\nbluex \u003Ctool.name> '\u003Cjson-input>'\nbluex list\nbluex \u003Ctool.name> --help\n```\n\nFor multi-line payloads, write JSON under `$BLUEX_WORKSPACE\u002F.bluex\u002Ftmp\u002F` and pipe with `cat`. Do not commit `.bluex\u002Ftmp`.\n\nUse `.bluex\u002Fartifacts\u002F\u003Ckind>\u002F\u003Cname>\u002F` for durable evidence the target repo should keep (fixtures, screenshots, reports, design inputs). Create the files first, then call `artifacts.create_repository` to write `artifact.json`; do not hand-write `artifact.json` manually. Do not register transcripts, secrets, scratch state, or routing\u002Fhandoff files as artifacts.\n\n## Tool reference\n\n\n| Tool                                               | Purpose                                                                                                        |\n| -------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- |\n| `issues.get`                                       | Read the issue snapshot.                                                                                       |\n| `issues.get_execution_context`                     | Issue, workspace, work, session, current PR.                                                                   |\n| `workspaces.get`                                   | Inspect the prepared workspace path.                                                                           |\n| `works.get`                                        | Read the current work reason and status.                                                                       |\n| `works.complete`                                   | Complete the current work; prefer `implementation.mark_ready` for normal handoff.                              |\n| `work_dependencies.list` \u002F `work_dependencies.get` | Explicit work dependencies — use instead of labels\u002Ftitles.                                                     |\n| `work_runnability.get`                             | Whether the current work is runnable; which blockers remain.                                                   |\n| `exchanges.list`                                   | Diagnostic paginated runner transcript search; not a replacement for public comments or handoffs.              |\n| `pull_requests.get`                                | Current linked PR.                                                                                             |\n| `pull_requests.list_review_threads`                | Synced review threads (filter by `resolutionState`).                                                           |\n| `pull_requests.list_review_comments`               | Synced PR review comments and submissions.                                                                     |\n| `pull_requests.list_decision_comments`             | Public PR handoff\u002Fvalidation\u002Freview\u002Fmerge decision comments.                                                   |\n| `pull_requests.resolve_review_thread`              | Resolve after the code or public comment evidence addresses it.                                                |\n| `pull_requests.register_github_identity`           | Register a PR's identity after `github.pull_requests.create` and sync GitHub branch\u002FSHA metadata.              |\n| `pull_requests.update_implementation_state`        | Record changed files and non-passing checks; resets review to pending. Call after registration and pushes.     |\n| `pull_requests.request_validation`                 | Enqueue host-owned local PR validation through Bluex and return the queued or deduped run.                    |\n| `git.status`                                       | Read local Git porcelain status.                                                                               |\n| `git.current_branch`                               | Read the current local Git branch.                                                                             |\n| `git.changed_files`                                | Read local changed file paths and statuses.                                                                    |\n| `git.create_branch`                                | Create one local Git branch without checking it out.                                                           |\n| `git.stage`                                        | Stage one explicit path set.                                                                                   |\n| `git.commit`                                       | Create one local commit from staged changes.                                                                   |\n| `git.push`                                         | Push one local branch to one remote.                                                                           |\n| `github.pull_requests.find_for_branch`             | Find GitHub pull requests for one branch through paginated REST.                                               |\n| `github.pull_requests.create`                      | Create one GitHub pull request only.                                                                           |\n| `github.pull_requests.get`                         | Read one GitHub pull request.                                                                                  |\n| `github.pull_requests.comment`                     | Create one GitHub PR conversation comment.                                                                     |\n| `github.pull_requests.review`                      | Submit one GitHub PR review.                                                                                   |\n| `github.pull_requests.merge`                       | Merge one GitHub pull request when the owning workflow permits it.                                             |\n| `github.pull_requests.diff`                        | Read one GitHub PR diff.                                                                                       |\n| `github.pull_requests.checks`                      | Read check runs for one GitHub PR head SHA.                                                                    |\n| `github.actions.failed_logs`                       | Read failed job logs for one GitHub Actions workflow run.                                                      |\n| `comments.create_issue_handoff`                    | Implementation handoff to the Bluex issue; accepts image `attachments`.                                        |\n| `attachments.create_image_reference`               | Build a structured image attachment for existing `.bluex\u002Fartifacts` or pinned repository images.               |\n| `artifacts.create_repository`                      | Register existing durable files under `.bluex\u002Fartifacts\u002F\u003Ckind>\u002F\u003Cname>\u002F`.                                       |\n| `implementation.mark_ready`                        | Finish implementation work; moves the issue to waiting.                                                        |\n| `works.block`                                      | Block when implementation cannot proceed; include the exact failing command\u002Foutput.                            |\n\n\nDiscover field shapes with `--help` before guessing.\n\nIssue-level Bluex handoffs must go through `comments.create_issue_handoff` and must return a Bluex `comment_...` id. If that tool fails, do not fall back to `github.issues.comment`, raw `gh`, or a connected GitHub app. Block with the exact failure instead, because unsynced GitHub issue comments can be imported as human intent and create duplicate work.\n\n## Repository recipes\n\n`git` and `gh` are on PATH in the prepared workspace, but prefer registered atomic tools when they cover the operation. Use raw shell for source inspection, edits, branch checkout, validation, and other repository commands that the tool list does not expose.\n\n### Open a new PR\n\n```bash\nBRANCH=\"bluex\u002F${ISSUE_ID}\"\nbluex git.create_branch \"{\\\"branchName\\\":\\\"$BRANCH\\\"}\"\ngit switch \"$BRANCH\" # raw shell justified: no registered atomic checkout tool exists\n# ... edit files ...\nbluex git.changed_files '{}'\nbluex git.stage \"$(jq -nc --argjson paths '[\"\u003Cchanged-path>\"]' '{paths:$paths}')\"\nbluex git.commit '{\"message\":\"Update agent workflow guidance\"}'\nbluex git.push \"$(jq -nc --arg branch \"$BRANCH\" '{remote:\"origin\",branch:$branch}')\"\nPR_CREATE_RESULT=$(bluex github.pull_requests.create \"$(jq -nc \\\n  --arg repo \"$REPO_SLUG\" \\\n  --arg head \"$BRANCH\" \\\n  --arg base \"main\" \\\n  --arg title \"\u003Ctitle>\" \\\n  --arg body \"\u003Cbody>\" \\\n  '{repo:$repo,head:$head,base:$base,title:$title,body:$body}')\")\nPR_NUMBER=$(printf '%s' \"$PR_CREATE_RESULT\" | jq -r '.result.json.number')\nPR_RESOURCE_ID=$(printf '%s' \"$PR_CREATE_RESULT\" | jq -r '.result.json.node_id')\nPR_GITHUB_METADATA=$(printf '%s' \"$PR_CREATE_RESULT\" | jq -c '.result.pullRequestIdentity.github')\nbluex pull_requests.register_github_identity \"$(jq -nc \\\n  --arg issueId \"$ISSUE_ID\" \\\n  --arg repoSlug \"$REPO_SLUG\" \\\n  --arg resourceId \"$PR_RESOURCE_ID\" \\\n  --argjson github \"$PR_GITHUB_METADATA\" \\\n  --argjson pullRequestNumber \"$PR_NUMBER\" \\\n  '{issueId:$issueId,repoSlug:$repoSlug,pullRequestNumber:$pullRequestNumber,resourceId:$resourceId,github:$github}')\"\nbluex pull_requests.update_implementation_state \"$(jq -nc \\\n  --arg pullRequestId \"pr_${REPO_SLUG\u002F\u002F[^a-zA-Z0-9]\u002F_}_${PR_NUMBER}\" \\\n  '{pullRequestId:$pullRequestId,checksStatus:\"pending\",changedFiles:[]}')\"\n```\n\n### Update an existing PR\n\n```bash\nbluex git.changed_files '{}'\nbluex git.stage '{\"paths\":[\"\u003Cchanged-path>\"]}'\nbluex git.commit '{\"message\":\"\u003Cconcise message>\"}'\nbluex git.push '{\"remote\":\"origin\",\"branch\":\"\u003Cbranch>\"}'\nbluex pull_requests.update_implementation_state \\\n  '{\"pullRequestId\":\"\u003Cid>\",\"checksStatus\":\"pending\",\"changedFiles\":[]}'\nbluex pull_requests.request_validation \\\n  '{\"pullRequestId\":\"\u003Cid>\",\"profile\":\"default\"}'\n```\n\n### Validate\n\n```bash\nbun test 2>&1 | tail -50\n# or whatever script the repo uses; check package.json\n```\n\n## Continuation turns\n\nWhen work was already in progress, keep the completion contract in view and read incrementally:\n\n1. Re-check the issue body or prior handoff if completion criteria are relevant.\n2. Read new comments since the last turn.\n3. Read CI output if `checksStatus` recently changed.\n4. Read review comments via `pull_requests.list_review_comments` \u002F `pull_requests.list_review_threads`; raw `gh pr view \u003Cnumber> --comments` is justified only if a required GitHub field is missing from registered primitives.\n5. Make the smallest sufficient delta without losing coverage of the contract.\n",{"name":5,"description":7},"main","2e94c321a368a0c3154b72811fcce4d56f383e47",".bluex\u002Fagents\u002Fui-implementer\u002Fskills\u002Fbluex-ui-implementer",0,"https:\u002F\u002Fgithub.com\u002Fgetbluex\u002Fbluex","https:\u002F\u002Fgetbluex.com","https:\u002F\u002Fgithub.com\u002Fgetbluex","https:\u002F\u002Fgetbluex.com\u002F","The open-source agentic execution layer. Ship from issues, not from chat.","2026-06-29 03:08:31",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add getbluex\u002Fbluex --skill bluex-ui-implementer",{"tool":65,"command":66},"bunx","bunx skills add getbluex\u002Fbluex --skill bluex-ui-implementer",{"tool":68,"command":69},"pnpm","pnpm dlx skills add getbluex\u002Fbluex --skill bluex-ui-implementer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgetbluex\u002Fbluex\u002Fblob\u002Fmain\u002F.bluex\u002Fagents\u002Fui-implementer\u002Fskills\u002Fbluex-ui-implementer\u002FSKILL.md",true,[],[74,80,90,96,110,116],{"skillNo":75,"name":76,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":44},"01M6KR6EW893TX7A0AJ5E2AXGN","example","https:\u002F\u002Fgithub.com\u002Fgetbluex\u002Fbluex\u002Fblob\u002Fmain\u002Fpackages\u002Fagents-runtime\u002Ftest-fixtures\u002Ffolder-agent\u002Fskills\u002Fexample\u002FSKILL.md",[],[76],{"skillNo":81,"name":25,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":86,"publishedAt":44},"01M6KR6AWRWBMB4KS8WWKFK5JJ","Explore, build, and refine UI.","https:\u002F\u002Fgithub.com\u002Fgetbluex\u002Fbluex\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fui\u002FSKILL.md",[85],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[25,87,88,89],"explore","build","refine",{"skillNo":91,"name":25,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":95,"publishedAt":44},"01M6KR66D1EGS7B4J2E5PJ3HE0","https:\u002F\u002Fgithub.com\u002Fgetbluex\u002Fbluex\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fui\u002FSKILL.md",[94],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[25,87,88,89],{"skillNo":97,"name":25,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":106,"publishedAt":44},"01M6KR624AB5M8PBXDRRF23ARV","https:\u002F\u002Fgithub.com\u002Fgetbluex\u002Fbluex\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fui\u002FSKILL.md",[100,105],{"categoryNo":101,"categoryName":102,"taxonomyType":103,"taxonomyTypeDesc":104},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[25,107,87,108,109,88,89],"MCP","fetch","webfetch",{"skillNo":111,"name":25,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":115,"publishedAt":44},"01M6KR5ZSMRR1YGC3TKAGGG46H","https:\u002F\u002Fgithub.com\u002Fgetbluex\u002Fbluex\u002Fblob\u002Fmain\u002F.bluex\u002Fagents\u002Fui-implementer\u002Fskills\u002Fui\u002FSKILL.md",[114],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[25,88,89,87],{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":44},"01M6KR5T99GDE0H1THB40GF9HP","shadcn","Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI. Provides project context, component docs, and usage examples. Applies when working with shadcn\u002Fui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for \"shadcn init\", \"create an app with --preset\", or \"switch to --preset\".","https:\u002F\u002Fgithub.com\u002Fgetbluex\u002Fbluex\u002Fblob\u002Fmain\u002F.bluex\u002Fagents\u002Fui-implementer\u002Fskills\u002Fshadcn\u002FSKILL.md",[],[118,123,124,125,126,127,128,25,129,130,131,132,133,134,135,136,137,138,29,139],"debugging","create","init","component","app","file","projects","context","styling","switch","project","triggers","false","component docs","codes","usage","components"]