hmj1026
- 37 skills
- 0 followers
- yesterday last updated
- ▌ Deploy List · hmj1026 bundleGenerate a deterministic deploy file-list (schema=v1) from git history. Use when: building a deploy/release checklist, 部署清單, or listing files to ship via --anchor, --deploy-commits, or base..head. Not for: commit lookup, raw diffs, or running the deploy. Output: a deploy checklist.
- ▌ Issue Analyze · hmj1026 bundleGitHub Issue and PR review thread deep analysis with an optional blind verdict. Purpose: analyze issue root causes, classify problems, plan investigations, or triage PR review comments for actionability. Not for: fixing bugs (use flow-drive), code exploration (use code-trace). Output: classified analysis + verdict assessment + investigation strategy.
- ▌ Module Design · hmj1026 bundleDesign or compare module responsibilities, public interfaces, and architecture trade-offs. Use when a boundary or adapter choice is unresolved. Supports design, review, compare, and bounded adversarial modes. Not for implementing a confirmed design, tracing code, or reviewing code correctness. Output: a bounded recommendation with evidence and verification needs.
- ▌ Openspec Artifact Guard · hmj1026 bundleUse when validating OpenSpec artifact shape, delta placement, task/git alignment, and safe change slugs. Apply while editing OpenSpec files or reviewing them before archive. Not for implementation or archive itself. Output: a verdict with artifact and task evidence.
- ▌ Legacy Characterization Tests · hmj1026 bundleWrite characterization tests for untested legacy code to lock current behavior before refactoring. Use when users want to safely refactor legacy controllers/models/services, add regression safety nets, or prepare code for extraction. Trigger words: characterization test, lock behavior, legacy test, safe refactor, 行為鎖定, 特徵測試, 安全重構. Not for: greenfield code, already well-tested modules, or pure bug fixes. Output: characterization test files + coverage delta report.
- ▌ Merge Prep · hmj1026 bundlePrepare a read-only branch merge analysis with native git merge-tree conflict detection and copy-pasteable manual commands. Use when deciding whether to merge one branch into another. Not for: checkout, merge, rebase, conflict edits, or branch mutation. Output: commits, files, conflicts, evidence, and manual commands.
- ▌ Pr Summary · hmj1026 bundleSummarize accessible open GitHub pull requests from structured gh JSON, filtering bots and grouping results by ticket. Use for a read-only PR status report. Not for: changing PR state, reviewing code, merging, or closing PRs. Output: grouped Markdown written to /tmp/pr-summary.md and displayed for copying.
- ▌ Repo Intake · hmj1026 bundleProject initialization inventory (one-time), for first onboarding a project or rebuilding cache after structural changes. Not for: day-to-day development (read cache directly), finding specific files (use code-trace). Output: project map with entrypoints + test map + next steps.
- ▌ Code Simplify · hmj1026 bundleUse when cleaning changed code for reuse, simplicity, efficiency, and the right abstraction level without changing behavior. Not for correctness review, broad redesign, or unbounded cleanup. Output: four-angle findings, applied/skipped changes, and baseline/final test evidence.
- ▌ Library Author · hmj1026 bundleAuthor and review published PHP/Laravel libraries, map testsuites, and plan version-matrix cells. Routes provider/facade design, Testbench setup, Composer contracts, polyfill audits, suite selection, and cell onboarding to separate modes. Not for application code or single-version framework advice. Output follows the selected mode.
- ▌ Feature Verify · hmj1026 bundleFeature verification (READ-ONLY, P0-P5). Purpose: verify feature behavior after deployment, validate API responses, diagnose production issues, or run a post-deploy smoke test. Not for: modifying data (use flow-drive), code review (use change-verdict), writing tests (use tdd-workflow), security audit (use change-verdict). Output: a P0-P5 verification report with pass/fail evidence per check.
- ▌ JS Static Checks · hmj1026 bundleJavaScript/TypeScript static-check status, ESLint tier setup, legacy-global synchronization, and progressive checkJs rollout. Use for lint/typecheck configuration or rollout tasks and check, setup, rollout actions. Not for everyday JS business logic. Output: read-only status, scoped configuration, or leaf migration evidence.
- ▌ Yii1 · hmj1026 bundleYii1.1 backend development, regression tests, framework hardening, and static security audit of controllers/models/configuration. Use for Yii1 request, AR/DAO, scenario, authorization, upload or session tasks. Not for Yii2, frontend-only work, or generic PHP language decisions. Output: compatible implementation evidence or a categorized framework audit.
- ▌ React · hmj1026 bundleReact runtime guidance for root setup, concurrent rendering, StrictMode effects, Actions, hooks, refs, and React 18/19 migrations. Use for version-specific React implementation or review after resolving the target package. Not for Next.js framework APIs or generic JS tooling. Output: target-scoped guidance, migration traps, and verification evidence.
- ▌ Swift · hmj1026 bundleSwift and iOS development, SwiftUI architecture, async tests, SDK privacy, Xcode/SPM builds, and asset-catalog icons. Use for Swift/iOS tasks or test, build, icon actions. Not for web/Android assets or general raster editing. Output: target-compatible implementation or review, verification evidence, or an imageset.
- ▌ Nextjs · hmj1026 bundleNext.js framework guidance for routing, typegen, typed routes, build tooling, async Request APIs, configuration, and Next.js 15.5/16 migrations. Use for version-specific Next.js implementation or review after resolving the target package. Not for standalone React APIs or generic JS tooling. Output: target-scoped guidance, migration traps, and verification evidence.
- ▌ Python · hmj1026 bundlePython service implementation or review, async FastAPI/SQLAlchemy APIs, pytest tests, and ruff/pyright/mypy setup or triage. Use for backend Python tasks. Not for frontend or non-Python work. Output: compatible typed code, offline tests, API guidance, or static-check configuration with evidence.
- ▌ Proposal Analyze · hmj1026 bundleUse when turning an initial proposal or proposal file into an evidence-backed implementation roadmap. Not for applying an approved OpenSpec change or writing OpenSpec artifacts. Output: validated assumptions, code-research summary, roadmap, alternatives, risks, and immediate actions.
- ▌ Opsx Apply Resume · hmj1026 bundleSave and resume a long-running OpenSpec apply session from a live worktree, preserving optional gates and host-specific handoff artifacts. Not for: starting a new proposal, changing the external OpenSpec workflow, or treating a commit as a prerequisite. Output: a saved/resumed handoff report with lifecycle and next-action evidence.
- ▌ Vue 2 Notes · hmj1026 bundleVue 2 (^2.5.17, Options API era) component structure and the reactivity caveats that bite when mutating reactive state. Use when writing or reviewing .vue single-file components in a Vue 2 project (resources/assets/js), or a codebase whose package.json pins vue ^2.5.x. Covers the data() / computed / methods / watch + lifecycle shape, props-down + $emit events-up, vue-loader SFC compilation, the Vue.set / array-mutation traps, and @vue/test-utils 1.x + vue-jest 3 testing. Not for Vue 3 or 2.7 Composition API (predates setup() / <script setup>) — load when touching components or planning a Vue 2 → 3 migration. Output: Vue 2 component guidance, migration traps, and verification gates.
- ▌ PHP · hmj1026 bundlePHP implementation, review, tests, runtime compatibility, and feature or library-floor decisions across PHP5.6,7.4,8.x. Use for language/runtime tasks and mixed-floor packages. Not for frontend-only work or Yii framework security/development ownership. Output: compatibility-safe code or decisions with runtime-matched verification.
- ▌ Laravel · hmj1026 bundleLaravel framework guidance across 5.4, 6, 7, 8, 9, 10, 11, and optional Mix 5. Use when implementing or reviewing framework-touching Laravel code, planning an upgrade, or debugging a version-specific build. Not for Symfony, Yii, or frontend-only work; use php for runtime selection. Output: one selected Laravel or Mix reference, compatibility constraints, and verification gates.
- ▌ Phpunit · hmj1026 bundleUse when writing, reviewing, or migrating PHPUnit 9, 10, or 11 tests, resolving a project version, or choosing assertion, metadata, provider, mock, hook, runner, or coverage APIs. Not for PHPUnit 5/6/7-only suites, everyday assertion writing without a version decision, or Laravel routing. Output: selected version boundary, applicable reference, migration guidance, and verification evidence.
- ▌ UI UX Verify · hmj1026 bundleRead-only check of one rendered page against one OpenSpec UI specification: content, structure, and behavior. Not for E2E authoring, application edits, data mutation, or API smoke tests. Output: a severity-ranked audit with APPROVE, WARNING, BLOCK, or UNAVAILABLE.
- ▌ Harness Setup · hmj1026 bundleConfigure or inspect the dhpk harness, or install selected host assets. Not for: ordinary harness audits, application changes, or silent credential/configuration changes. Output: a host-specific setup report with preserved-file, receipt, and terminal evidence.
- ▌ Change Verdict · hmj1026 bundleReview code, PRs, security, tests, documents, change risk, pending changes, or dependency vulnerabilities. Verdicts are read-only; explicit dependency fixes go to an authorized writer. Not for source repair or architecture-only design. Output: evidence-backed findings and review status.
- ▌ Release Creator · hmj1026 bundleCuts a new release of a software project or plugin, coordinating release configuration, version files, changelog, validation, and the fixed git/PR/tag/CI sequence. Not for: PHP package publication or ordinary commits. Output: a validated release preparation or publication result with the human merge gate preserved.
- ▌ Git Smart Commit · hmj1026 bundle將雜亂的 git 變更依邏輯分群、逐批提交,適用於需要把多項變更拆成多個邏輯一致 commit 的情境。Not for: 單一小變更或只需要一個 commit(直接 commit 即可)。Output: 可直接執行的分組提交計畫與 commit 指令。
- ▌ Flow Guide · hmj1026 bundleRead-only workflow guidance and bounded routing. Use when work needs a route, policy lookup, next action, closeout gate, or Codex usage help. Not for implementation, review, code tracing, or skill authoring. Output: one typed report with evidence and a clear handoff.
- ▌ Repo Verify · hmj1026 bundleRun a repository verification loop with runner-first execution, deterministic stages, and explicit PASS/FAIL/SKIP output. Use for fast or full validation of a consumer repository. Not for: mutation, fixing failures, dependency remediation, or merge approval. Output: runner summary or a complete fallback stage table.
- ▌ Doc Maintain · hmj1026 bundleMaintain documentation through stale-doc refresh, architecture codemap generation, or a bounded Markdown refactor. Selects update, codemap, or refactor while preserving each output and evidence contract. Not for application source, tests, manifests, route tables, generated projections, or broad policy review.
- ▌ Tdd Workflow · hmj1026 bundleUse for test-first feature or bug implementation, regression tests, and choosing public test seams or boundary mocks (RED-GREEN-REFACTOR). Not for Playwright journeys, coverage audits, or docs/format/rename-only work. Output: scoped tests or code with RED/GREEN evidence.
- ▌ Create Pr · hmj1026 bundleCreate a GitHub pull request from a pushed branch with ticket-aware title and body generation. Not for: committing, pushing, merging, releasing, or editing an existing PR. Output: a dry-run gh pr create command by default, or the created PR URL after explicit execution.
- ▌ Precommit · hmj1026 bundleRun the deterministic pre-commit pipeline in fast or full mode through the packaged runner. Use when handing off repository changes. Not for: ad hoc replacement checks, dependency audits, or read-only verification. Output: runner-owned changed-file reporting and final verdict.
- ▌ Code Trace · hmj1026 bundleTrace unfamiliar code, diagnose a reproducible failure, investigate history, or pick a code-navigation tool, following symbols, callers, data flow, or regressions. Not for implementing a fix, reviewing a diff, or plain-text search. Output: an evidence-backed trace or root cause.
- ▌ Flow Drive · hmj1026 bundleUse the current Host and Model to complete one bounded, authorized task and report observed verification evidence or a precise blocker.
- ▌ Notebooklm Course Builder · hmj1026 bundle以條件式瀏覽器自動化或 14 階段嚮導建構 NotebookLM 課程教材。適用於:(1) 將課程大綱轉為包含來源引用、逐節講義、Quiz 與 Study Guide 的完整課程;(2) 規劃 Notebook 與研究分群、來源審核、Coverage 分析;(3) 自動操作 NotebookLM 或延續既有建置進度。