- Skills
- 83
- 仓库
- 1
- 职业覆盖
- 3
- 场景覆盖
- 5
- Stars
- ★ 34
Atomic 的 Skills 83
explore-pr
Build an interactive, design-first and picture-first exploration page for a pull request — its architecture, abstractions and design decisions drawn as diagrams, a guided tour in reading order with code as the evidence, an attention map of where the risk sits, a ledger of its riskiest operations, prior review findings re-checked against the code, and simulations specific to the PR — with the reviewer's verdicts and notes saved. Use when the user wants to explore, understand or review a large pull request or its design, asks for a review page, walkthrough or visual explanation of a PR, or is struggling to review a big change.
update-work-item
Update fields (status, priority, tags, parent, etc.) of an existing work item. Use to transition status, change priority, manage tags, or edit any frontmatter field. No transition enforcement — arbitrary changes are allowed.
sync-work-items
Reconcile local work items in meta/work/ with the active remote tracker named by work.integration. Use when the user wants to sync, push, or pull work items to or from Jira or Linear, preview what a sync would change, or reconcile divergent local and remote state.
sync-work-items-recovery
Recovery procedures for work sync failures that need a person — terminal rows, refused pending pushes and refused orders. Read by sync-work-items — not invoked directly.
stress-test-work-item
Interactively stress-test a work item by grilling the user on scope, assumptions, acceptance criteria, edge cases, and dependencies to surface issues, gaps, and flawed assumptions before implementation is planned.
review-work-item
Review a work item through multiple quality lenses and collaboratively iterate based on findings. Use when the user wants to evaluate a work item before implementation or escalation.
rekey-work-items
Converge every work item's ID onto the configured work.id_pattern, renaming files and rewriting references across meta/. Use after changing work.id_pattern or work.key, when existing work items should take IDs in the new shape, or to finish or undo an interrupted re-key.
refine-work-item
Interactively refine a work item by decomposing it into children, enriching it with codebase context, sharpening its acceptance criteria, sizing it, or linking it to dependencies. Use after a work item has been drafted and before planning begins.
list-work-items
List and filter work items from the configured work directory. Use when discovering what work items exist, filtering by status/kind/priority/parent/tag, or viewing the work item hierarchy.
extract-work-items
Extract work items in batch from existing documents (specs, PRDs, research, plans, meeting notes, design docs). Use whenever the user wants to capture, pull out, or convert requirements, work items, user stories, bug reports, or actionable tasks from existing files into structured work items in meta/work/ — even if they don't say "extract" explicitly.
create-work-item
Interactively create a well-formed work item. Use when capturing a feature, bug, task, spike, or epic as a structured work item in meta/work/.
visualise
Open the accelerator meta visualiser. Launches the companion-window server in the background and returns a URL. Subcommands stop and status manage the running server.
commit
Create VCS commits for session changes. Use when the user wants to commit their work with well-structured, atomic commits.
work-item-review-output-format
Output format specification for work-item review agents. Defines the JSON schema, field reference, severity emoji prefixes, and finding body format for work-item reviews. Used by review orchestrators — not invoked directly.
pr-review-output-format
Output format specification for PR review agents. Defines the JSON schema, field reference, severity emoji prefixes, and comment body format for PR reviews.
plan-review-output-format
Output format specification for plan review agents. Defines the JSON schema, field reference, severity emoji prefixes, and finding body format for plan reviews.
usability-lens
Usability review lens for evaluating developer experience, API ergonomics, configuration complexity, and onboarding. Used by review orchestrators — not invoked directly.
testability
Work-item review lens for evaluating whether Acceptance Criteria and requirements admit a concrete verification strategy — each criterion must be specific, measurable, and verifiable. Used by review orchestrators — not invoked directly.