1천건 · 관련도순
Trace what an actual code change could break beyond its diff when interfaces, serialized data, database schemas, configuration, caches, lifecycle ordering, or cross-language consumers are involved. Use for explicit impact analysis; not local renames, prose edits, ordinary dependency bumps, or generic architecture discussion.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
First-principles assumption auditor. Classifies each hidden assumption (fact / convention / belief / interest-driven), ranks by fragility × impact, and rebuilds conclusions from verified premises. Bilingual: auto-detects Chinese or English.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
You bring the third dimension to the web. You know when 3D enhances and when it's just showing off. You balance visual impact with performance. You make 3D accessible to users who've never touched a 3D app. You create moments of wonder without sacrificing usability.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review this card's specs with fresh eyes for gaps, contradictions, and cross-spec impact
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Check upgrade safety for a Tamanu upgrade that spans many versions: verify that every intermediate hotfix is included in the target version, and surface the new configuration/settings, data migrations, and FHIR rematerialisation impact the upgrade brings. Use when the user wants to check an upgrade from one Tamanu version to another (e.g. "check hotfixes from v2.31 to v2.47"), confirm no intermediate hotfix was dropped, or understand what config, migrations, and FHIR rework a multi-version jump requires. Handles Tamanu's train-release model (release/X.YY branches vs vX.YY.Z patch tags) and the cherry-pick model where the same logical fix has different SHAs on different branches. Purely git-based — no live database or Canopy access needed. Not for cutting a release (see release-cutoff-checks) or deciding which tests to run (see scope-tamanu-release-tests).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Produce a release test-impact analysis for a Tamanu version upgrade: compare two Tamanu releases and classify every functional area as Full Test, Smoke Test, or Skip, each with a short reason and the Linear card or PR reference. Use when the user wants a test plan, QA scope, regression scope, or "what to test" for a Tamanu release or upgrade, wants to compare or diff two Tamanu versions (e.g. v2.57 to v2.59), or asks which areas changed between two releases. Handles Tamanu's train-release model (release/X.Y branches vs vX.Y.Z tags) and maps changed files and PRs to Tamanu functional sections (Patient Management, Encounters/Charting, Surveys & Programs, Medications, Labs, Imaging, Appointments, Vaccinations, Sync, Settings, Reports, Admin/Permissions, Mobile, etc.). Optionally maps against a regression-testing spreadsheet's sections when one is provided.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Compares one policy against one requirement set (standard, regulation, contract schedule or customer requirement) clause by clause and returns a draft gap review: each requirement element, the policy clause that appears to address it, an apparent match state, and every gap as a question with the clause reference on both sides. Never concludes that the policy complies; the owner decides. Use when the user asks to "gap our policy against the standard", "map this policy to the regulation clause by clause", "check the security policy against the customer's contract schedule", "compare our policy with the new edition" or "where does our policy fall short of the requirements". Do not use for mapping a requirement to the operating controls that implement it, use controls-gap-pack instead; for what a regulatory change means for the organisation, use regulatory-change-impact-note. Drafts for human review; never approves, authorises or signs off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Proposes redactions of personal identifiers in pasted text or an attached document (names, contact details, identification and account numbers, dates that identify, quasi-identifiers) and returns a DRAFT redacted copy with consistent placeholder tokens plus a redaction table stating what was replaced, where and why, with a confidence level and a blank reviewer decision per row. Use when the user asks to "redact the names in this document", "de-identify this transcript before we share it", "strip personal data from these notes", "anonymise this report for publication" or "what would need redacting here". Do not use for assessing a planned processing activity, use dpia-draft-pack instead; do not use for working out what data an incident exposed, use data-incident-impact-brief instead. Never declares a document anonymised, safe to release or compliant. Drafts for human review; never approves, authorises or signs off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reviews a proposal, business case, deck, plan or restructuring paper in character as a Chief Human Resources Officer archetype and returns a DRAFT review with a verdict, findings that cite the exact passage, people and organisation risks, what would change the verdict and five interrogation questions. Use when the user asks to "run a CHRO review", "what would HR say about this", "pressure-test the people impact" or "prepare this for the people committee". Do not use for the employee representatives' own view of a plan, use works-council-reviewer instead. Drafts for human review; never approves, authorises or signs off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Resolve complex or high-impact problems when the cause, solution path, requirements, or proof boundary is genuinely uncertain. Use when work needs evidence-led diagnosis, consequential design or implementation, or a completion audit; do not trigger merely because work has multiple steps, or for simple facts, fully specified routine changes, or pure creative generation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
IT要求・活動インパクトスコアの良い点・悪い点を分析し、改善点と改善のための問いを生成
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
IT要求・活動のインパクトスコアを算出
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
検証結果に基づいてIT要求・活動インパクトスコアを洗練・修正する
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
IT要求・活動インパクトスコアの検証を行う時の観点を説明する
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Answer whether a specific advisory reaches anything in THIS repository — which manifest declares the package, at what version, whether the version is in range, and whether the vulnerable code is reachable. Use when someone asks "does CVE-… affect us", when triaging an advisory against a real codebase, or before spending effort on a fix.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run lint checks for VK.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Archive multiple completed changes at once. Use when archiving several parallel changes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.