Loading...
Loading...
Found 11,570 Skills
Summarizes an RHDH sprint that has finished or is finishing, from Jira RHIDP, RHDHPLAN, RHDHBUGS, and RHDHSUPP: committed versus completed story points, scope added mid-sprint, per-member breakdown, epic progress, the demo checklist with RHDH file and slide naming, and the velocity trend. Use for "sprint report", "what did we complete this sprint", "sprint review prep", "how did the sprint go", or "which demos do we owe". Looks back at work already done; preparing the sprint that has not started yet is a different job, and a single issue such as RHIDP-1234 is not a sprint.
Full spec-driven pipeline — walks brief → tokens → shape (spec) → craft (build) → converge → ship in one guided run. Writes `.ui-craft/spec.md`. Run when starting a net-new surface from scratch. Invoke when the user asks for sddesign on their UI, or mentions 'sddesign' alongside design / UI / frontend work.
(NS) Ad-hoc coding worker — bug fixes, small refactors, scripts, migrations — without full SDD. Entry priority 5: use for "just implement this", "quick fix", or concrete coding without execution-handoff (also C2 under ns-code-autonomous). Do NOT use for GitLab ISSUE_URL (ns-execution-gitlab-issue), multi-day/version scope (ns-spec-driven), diagnosis-only (ns-code-investigator), or when execution-handoff.md exists. Do NOT generate requirements/tasks/handoff.
Upgrade an ObjectStack metadata project across a protocol major — run the deterministic conversion chain, then work the semantic residue the chain cannot express (intent choices, custom code on retired APIs, stale prose) to a decision with the project's owner, and finish with a green `validate` plus a human-readable upgrade report. Use when a project is on an older protocol major and must move to the current one, when `@objectstack/spec` was bumped across a major and metadata or code stopped parsing, when a parse or `tsc` error quotes a `[REMOVED]` prescription, or when asked to "upgrade to v17" / "升级到 v17" / "一键升级元数据项目". Do not use to author new metadata (the domain skills cover that), to design a retirement in the ObjectStack platform repo itself (that is the platform's own internal playbook), or to hand-write a rewrite the conversion chain already applies — running the chain is always the first step, never a fallback.
Commit the current agent's changes by default, or all working-tree changes when explicitly requested, with clean logical grouping and repository commit-message conventions. Use when the user asks to commit changes, commit this work, commit all changes, split changes into commits, propose commit messages, or wait for "go" before committing.
Apparel Image Generation (for models/clothing). Supports single images or image sets: white background images (invisible model), model images, lifestyle marketing images, selling point images, A+ images, size chart images. Direct generation for single image of a single type; automatic orchestration and planning for multiple images of multiple types. Triggered when users upload model images or apparel images (topwear, bottomwear, dresses, outerwear, shoes & hats, etc.) and request actions like "create an image set", "make a model image", "make a lifestyle marketing image", "make a selling point image", "make an A+ image", "make a size chart image", "make a white background apparel image". Pure image editing operations go through linkfox-aigc-imagegen.
Trim a spec, ADR set, or design doc down to what a builder needs, without losing a fact. TRIGGER when: user says a spec is 'too long' or 'bloated'; user asks what to remove from it, or wants it cut to 'just what we need to build'.
Completes one or more tasks. Creates one tested and reviewed pull request for each task. Use to implement, build, fix, or deliver tasks, tickets, pull requests, or a milestone.
Составляет однозначный план реализации без написания кода. Используй, когда пользователь явно просит составить, подготовить или расписать план реализации, внедрения либо исправления. Не используй, когда пользователь хочет обсудить варианты и ещё не выбрал решение, просит зафиксировать только желаемый результат без шагов, сразу реализовать задачу или провести ревью изменений.
Знакомит пользователя с набором ai-bro, картой скиллов и типовым порядком работы. Используй только при явном вызове /bro-on-board для первого знакомства или повторного прохождения онбординга. Не используй для общих вопросов о проекте или работе других инструментов.
Use after an AI coding session or before commit, PR, handoff, or release when the operator wants a human-readable summary of what was done and why, with key files and current state, without a long audit.
Run one dev-loop session as the driver - preflight, select, one spec end to end. Harness-generic - grooming drafts and takes run in fresh native subagents of whatever harness drives, takes in their own worktrees (an explicit invocation request may route takes through a runner file instead); the gate stays yours.