'factory' 검색 결과

Review a GitLab merge request linked to a Factory work item, verify the current commit, and publish findings with a test report. It records the review verdict on the card and prepares a session handoff without merging.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review a GitLab merge request assigned through Factory
• Verify earlier review findings against the current commit
• Publish test results and an evidence-based verdict

Review a pull request in a Factory work session by investigating its purpose, history, implementation, tests, and security. Publish verification results and a review verdict, then record the outcome on the work card.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing a pull request assigned through Factory
• Checking whether a bug fix addresses the underlying cause
• Verifying findings from bots and human reviewers

Helps adapt LLMs to specific tasks with LLaMA-Factory, including training through a web interface and memory-saving methods such as QLoRA. Provides documentation references for learning features, implementing workflows, and investigating code problems.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Exploring LLM fine-tuning through a web interface
• Checking LoRA and QLoRA training options
• Investigating LLaMA-Factory implementation problems

Re-review a pull request after new commits arrive. Check every previous finding, inspect the new changes for regressions, and review the full current change. Run relevant verification and publish a test report and review verdict within Factory.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking whether previous review findings were addressed
• Finding regressions introduced by follow-up commits
• Re-running tests against the current PR head

Review and test a pushed Factory branch before a pull or merge request is opened. Record findings against the exact tested commit, then approve the work or return it to the builder with actionable changes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing a branch before opening a pull request
• Checking whether earlier review findings were fixed
• Recording test results and required changes

Update the GitHub issue linked to completed Factory work after verifying the target repository. Remove specified triage labels and, for open issues, add a pending-close label and completion comment without closing the issue.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Updating an issue after Factory work is complete
• Removing triage labels from completed work
• Adding a pending-close label and completion comment

Turn a Factory work item into a phased implementation plan grounded in current code and project history. Document scope, changes, tests, risks, and assumptions, then hand the plan to the execution stage.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Planning implementation after issue triage
• Defining changes and verification for each phase
• Recording design choices and rejected alternatives

Investigates GitHub or Linear issues through code, change history, and reproduction attempts. Produces a structured handoff covering causes, assumptions, effort, and impact, then requests the appropriate Factory workflow stage update when applicable.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating the root cause of a reported bug
• Checking for duplicate issues or regressions
• Preparing findings for whoever plans the fix

Configure Factory board behavior and GitHub or Linear event handlers in deployment code. Adjust stage transitions, phase meanings, and tool-result handling, then check the changes with focused tests and versioned audit records.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Add approval requirements to board transitions
• Change GitHub or Linear event handling
• Define custom board phases and tool-result rules

Get guidance on adapting LLMs through additional training with LLaMA-Factory. The skill covers a visual interface requiring no code, LoRA and QLoRA training methods, and documentation-based help with implementation, features, and debugging.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Learning additional training through a visual interface
• Exploring LoRA and QLoRA training methods
• Checking supported models and multimodal features

Generates PSR-17 HTTP Factories implementation for PHP 8.5. Creates RequestFactoryInterface, ResponseFactoryInterface, StreamFactoryInterface, UriFactoryInterface, ServerRequestFactoryInterface, UploadedFileFactoryInterface. Includes unit tests.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Run a spec-driven agent loop where coding tasks live as markdown specs that move through inbox → active → archive, get implemented by Claude Code or Codex, and pass a review gate before they count as done. Use when the user mentions "loop factory", a "spec-driven loop", an "agent factory", wants repeatable/reviewable agent work, or when a repo has a factory/specs/inbox or factory/specs/active directory. Also covers installing and scaffolding the loop-factory CLI into a project.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Auto-activate for polyfactory, ModelFactory, DataclassFactory, MsgspecFactory, AttrsFactory, Use, register_fixture, pytest plugin, __random_seed__, or coverage(). Not for production seeding.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when orchestrating Loop Factory specs from factory/specs/inbox or factory/specs/active, dispatching work to Codex or Claude agents, generating implementation prompts, or deciding next loop state.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when orchestrating Loop Factory specs from factory/specs/inbox or factory/specs/active, dispatching work, generating implementation prompts, or deciding next loop state.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Re-review a GitLab merge request after new commits, track the outcome of every previous finding, and inspect both new changes and the full proposal. Verify the current code, then publish a test report and review verdict.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Re-reviewing a merge request after fixes
• Tracking the resolution of earlier review findings
• Checking new commits for regressions and incomplete fixes

Add datasets, models, and other components to machine learning projects using consistent registration and creation patterns. The skill guides file placement, configuration, and automatic module loading so new components fit the project's established architecture.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adding a registered Dataset class
• Creating a model driven by configuration
• Wiring registration and creation logic in a new module

Add datasets, models, and other components to machine learning projects using consistent registration and creation patterns. The skill guides file placement, configuration, and automatic module loading so new components fit the project's established architecture.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adding a registered Dataset class
• Creating a model driven by configuration
• Wiring registration and creation logic in a new module

Verify an open factory PR before human review - re-runs gates, checks the test proves the fix, checks scope and test tampering. Use when reviewing a factory PR, running the PR review routine, or asked to independently check a change.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

供应链与生产运营 (供应链与生产运营 (Supply Chain & Production Operations) — 面向制造业与消费品实体供应链的『计划-制造-交付』运营判断,不是采购谈价技巧,也不是跨境电商发货物流。覆盖: (a) 第一性张力 — 这行的核心世界观分歧: **流动 > 局部效率(用有效产出/流动时间看系统,而不是用设备利用率/人均产出看工位;非瓶颈上的效率是幻觉) ⇄ 精益拉动 vs 推式预测(TPS/JIT 按下游消耗拉动、小批量平准化 vs MRP 按预测展开净需求推动;DDMRP 解耦缓冲是第三条路) ⇄ 精益/丰田 TPS 派 vs 约束理论 TOC 派(消除七大浪费、全局改善 vs 五步聚焦瓶颈、鼓-缓冲-绳 DBR 排产;两派互相指责对方浪费时间/只治标) ⇄ 变异是敌人(Deming/六西格玛/Factory Physics 的 VUT 排队论: 利用率越靠近满载排队时间越爆炸,交期长不是产能不够而是变异+高负荷) ⇄ 库存是负债 vs 库存是缓冲(会计把库存记成资产、精益视其为掩盖问题的水位、TOC 与韧性派视其为吸收变异的必要缓冲;真问题是缓冲放在哪一层而不是有没有) ⇄ 精益 JIT vs 韧性冗余(2020-2023 断链后 just-in-case、多源、近岸/友岸的回摆;精益派反驳崩的是『假精益』——单一来源+砍库存不砍变异) ⇄ 服务水平 vs 库存成本(安全库存/报童模型/ABC-XYZ 的经典取舍,牛鞭效应放大上游波动) ⇄ 成本导向压价 vs 供应商共生开发(Kraljic 分级、丰田供应商协会式长期共生 vs 年降指标与竞价) ⇄ 一个数 vs 各部门各算各的(S&OP/IBP 的本质是跨职能对齐到一套数字与一份产销计划))**; (b) 工具栈(此行的工具是『系统+方法』的混合) — ERP/MRP(SAP S/4HANA PP·MM、Oracle、用友·金蝶、Odoo、NetSuite)、APS 高级计划排程(Kinaxis RapidResponse、o9、Blue Yonder、SAP IBP、OMP、Siemens Opcenter APS)、MES/车间执行(Siemens Opcenter、Rockwell FactoryTalk、黑湖智造)、WMS/TMS、需求预测(统计模型 + Nixtla StatsForecast/Prophet、FVA 预测增值分析)、运筹优化与仿真(OR-Tools、Gurobi、Pyomo、AnyLogic、FlexSim、SimPy)、供应链风险与多级可视(Resilinc、Everstream、Interos)、分析层(SQL/Python pandas/Power BI)、以及纸笔工具(价值流图 VSM、A3、看板、标准作业票)—— 选型决策树的关键分岔是 MTS/MTO/ATO/ETO 履行模式与需求变异度,而非厂商功能清单; (c) 心智模型层 — 利特尔法则(在制品 = 产出率 × 流动时间)、瓶颈与非瓶颈、缓冲三态(库存/时间/产能缓冲)、解耦点(客户订单渗透点 CODP)、牛鞭效应、takt time 节拍与产线平衡、OEE 与六大损失、muda·mura·muri 三种浪费、自働化 jidoka 与安灯、防错 poka-yoke、SMED 快速换模换出小批量、平准化 heijunka、PDCA 与丰田改善型 Toyota Kata、DMAIC 与 Cpk 过程能力、报童模型与安全库存公式、ABC-XYZ 分级; (d) 工作流/SOP — 跑一轮月度 S&OP(需求评审→供应评审→预 S&OP→执行 S&OP)、做需求预测与预测误差复盘(MAPE/WMAPE/bias/FVA)、设定库存分级与安全库存、MRP 跑批与例外消息处理(缺料齐套与 MRP 神经质)、瓶颈识别与 DBR 排产、价值流图现状图→未来图→改善计划、新品导入 NPI 与多级 BOM/ECN 工程变更、供应商选择与开发(RFQ→审厂→APQP/PPAP→量产→年度绩效)、断料应急与交期承诺(ATP/CTP)、循环盘点与库存准确率; (e) 知识正典(en/ja 一手极厚,中译齐全) — 《目标 The Goal》Goldratt(TOC 小说体奠基)、《丰田生产方式》大野耐一、《改变世界的机器》Womack·Jones·Roos(MIT IMVP 研究)、《精益思想 Lean Thinking》Womack & Jones、《丰田模式 The Toyota Way》Liker、《工厂物理学 Factory Physics》Hopp & Spearman(排队论视角的运营科学)、《学习观察 Learning to See》Rother & Shook(VSM)、《丰田套路 Toyota Kata》Rother、Spear & Bowen 的 HBR 1999《Decoding the DNA of the Toyota Production System》、Lee/Padmanabhan/Whang 1997《The Bullwhip Effect in Supply Chains》、Ptak & Smith 的 DDMRP、Orlicky 的 MRP、Chopra & Meindl 的供应链管理教材、Deming《转危为安 Out of the Crisis》、Sheffi《The Resilient Enterprise》、ASCM/APICS 的 SCOR 参考模型与 CPIM/CSCP 知识体系; (f) 行业大佬/figures — 大野耐一(TPS 立法者)、新乡重夫(SMED/防错)、Eliyahu Goldratt(TOC 创立者)、W. Edwards Deming(变异与系统观)、James Womack & Daniel Jones(把 TPS 译成西方可学的『精益』)、Jeffrey Liker(丰田模式学术化)、Mike Rother(VSM 与改善型)、Wallace Hopp & Mark Spearman(工厂物理学)、Hau Lee(斯坦福,牛鞭效应与 Triple-A 供应链)、Yossi Sheffi(MIT,韧性)、Carol Ptak & Chad Smith(DDMRP)、David Simchi-Levi(MIT,风险敞口指数)、Steven Spear(TPS 的 DNA)、以及中文圈的供应链实务作者(刘宝红等); (g) 争议/批判(必须保留不洗白) — JIT 是不是 2021 全球断链的元凶(精益派反驳:崩的是单一来源+砍库存不砍变异的『假精益』);西方学精益的高失败率(只搬工具不搬思维,精益在很多工厂沦为裁员的代号);六西格玛黑带官僚化与扼杀创新之争;TOC 派与精益派互相攻击(Goldratt 讽刺精益是等浪费自己浮现);预测无用论(需求驱动派说预测必然错、要靠缓冲吸收)vs 统计预测派;控制塔/数字孪生/AI 预测的过度承诺与高项目失败率;中国制造的年降与内卷式压价 vs 供应商共生;近岸·友岸外包是真实产能转移还是政治叙事; (h) 流派/思想谱系 — **精益/TPS 派(丰田血统:大野-新乡→Womack/Jones/Liker/Rother,信全局消除浪费与人的改善能力)** vs **约束理论 TOC 派(Goldratt:系统产出只由瓶颈决定,聚焦五步、DBR、缓冲管理)** vs **统计质量/六西格玛派(Deming-Juran-Shewhart→GE/Motorola,信减少变异与过程能力)** vs **运营科学/工厂物理学派(Hopp & Spearman:用排队论与数学定律解释,认为精益与 TOC 都是特例)** vs **需求驱动/DDMRP 派(Ptak & Smith:预测不可靠,靠战略解耦缓冲)** vs **韧性/风险派(Sheffi、Simchi-Levi:效率之外必须为断链设计)**。不含: 跨境电商卖家的发货与头程物流(已由 cross-border-ecommerce 覆盖)、纯采购的商务谈判技巧、企业级 ERP 的代码实施与二次开发、通用项目管理。) Master OS — automated mastery of 供应链与生产运营 (Supply Chain & Production Operations) — 面向制造业与消费品实体供应链的『计划-制造-交付』运营判断,不是采购谈价技巧,也不是跨境电商发货物流。覆盖: (a) 第一性张力 — 这行的核心世界观分歧: **流动 > 局部效率(用有效产出/流动时间看系统,而不是用设备利用率/人均产出看工位;非瓶颈上的效率是幻觉) ⇄ 精益拉动 vs 推式预测(TPS/JIT 按下游消耗拉动、小批量平准化 vs MRP 按预测展开净需求推动;DDMRP 解耦缓冲是第三条路) ⇄ 精益/丰田 TPS 派 vs 约束理论 TOC 派(消除七大浪费、全局改善 vs 五步聚焦瓶颈、鼓-缓冲-绳 DBR 排产;两派互相指责对方浪费时间/只治标) ⇄ 变异是敌人(Deming/六西格玛/Factory Physics 的 VUT 排队论: 利用率越靠近满载排队时间越爆炸,交期长不是产能不够而是变异+高负荷) ⇄ 库存是负债 vs 库存是缓冲(会计把库存记成资产、精益视其为掩盖问题的水位、TOC 与韧性派视其为吸收变异的必要缓冲;真问题是缓冲放在哪一层而不是有没有) ⇄ 精益 JIT vs 韧性冗余(2020-2023 断链后

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the user wants a research-paper figure Skill Factory: build, patch, package, or use reusable specialized paper-figure-making skills from lawful literature/corpus evidence. Generated skills must use a specialized-skill-first workflow, full-feasible local PDF coverage where available, startup-plan-only first replies, target-paper candidate/final image isolation, mandatory image-embedded visual-structure explanation, mandatory non-target concept/modeling example display for abstract visual decisions, saved subtype/style illustration atlases, ChatGPT web Create image / ChatGPT Images 2.0 rendering, Codex $imagegen-first rendering, sample-image transfer rules, all-step/current-position state footers, and a mandatory first-round diverse candidate board followed by P6b/P6c paper-local best-practice optimization before final prompt construction.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Verify an open factory PR before human review - re-runs gates, checks the test proves the fix, checks scope and test tampering. Use when reviewing a factory PR, running the PR review routine, or asked to independently check a change.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Busabase-backed project-based PPT production App-in-Skill. Use when the user invokes $kelly-ppt-factory or /kelly-ppt-factory, mentions PPT factory, 规模化 PPT, bulk PPTX, batch decks, reusable PowerPoint style systems, presentation production workflows, pitch decks, sales decks, training decks, report decks, slide-card/storyboard planning, style-consistent deck generation, PPTX QA, or wants to manage many PPTX files through project to deck to slide card to review to generate to render QA.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Django 모델, 화면, API를 테스트부터 작성해 구현하고 검증합니다. 테스트 데이터 생성, 외부 서비스 모의 처리, 코드 커버리지 확인도 다룹니다.

• 테스트부터 Django 기능 개발하기
• API 인증과 입력 검증 확인하기
• 재사용할 테스트 데이터 준비하기