OpsMill

General code quality review — project guideline compliance, bug detection, code quality analysis.

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

Run a session retrospective that surfaces context-management gaps and routes them to approved follow-up actions.

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

Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.

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

Stages and commits the current changes onto a safe working branch, enforcing branch discipline and optionally pushing upstream. TRIGGER when: the user wants to commit, save, or check in the current changes. DO NOT TRIGGER when: opening a pull request → pr.

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

Generate a custom checklist for the current feature based on user requirements.

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

Code comment accuracy verification, documentation completeness assessment, comment rot detection.

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

Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.

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

Analyzes recent CI failures on pull requests to identify flaky tests, using retry outcomes (failed attempt → green re-run) and cross-PR recurrence as evidence, and maintains a local longitudinal ledger so flakiness can be tracked over time. TRIGGER when: the user wants to find flaky tests, correlate recent CI failures, check which tests fail across PRs or recover on retry, or refresh the flakiness trend report. DO NOT TRIGGER when: babysitting a single PR's CI until green → monitoring-pull-requests; diagnosing or fixing one specific failing test → the bug-analysis skills.

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

Run the full speckit workflow end-to-end — specify, plan, critique, tasks, implement, review — making all decisions autonomously. Stops before extract; run that manually.

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

Perform a dual-lens critical review of the specification and plan from both product strategy and engineering risk perspectives before implementation.

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

Synthesises the current conversation context into a Product Requirements Document and publishes it to GitHub (as a comment on a referenced issue, or a new issue). Synthesises from context; does not interview. TRIGGER when: the conversation has produced enough understanding of a feature and the user wants it captured as a PRD. DO NOT TRIGGER when: a single small issue is enough → creating-issues; the idea has not been stress-tested yet → grilling-ideas first; bug reports.

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

Error handling review — silent failure detection, catch block analysis, error logging.

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

Comprehensive code review using specialized agents — orchestrates code, comments, tests, errors, types, and simplify agents sequentially.

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

Rebases a feature branch onto its latest base, resolving conflicts while preserving the intent of local changes, optionally force-pushing and watching CI afterward. TRIGGER when: the user wants to rebase a feature branch, update a branch against its base, or replay local work on top of the latest upstream. DO NOT TRIGGER when: merging a release branch into dev → merging-branches; only watching CI on an already-open PR → monitoring-pull-requests.

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

Validate Jira/JPD ticket reference and create a feature branch

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

Execute the implementation plan by processing and executing all tasks defined in tasks.md

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

Run the speckit implementation phase chunk-by-chunk in clean-context subagents, then review, then produce a final report. Picks up from an existing tasks.md.

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

Execute the implementation planning workflow using the plan template to generate design artifacts.

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

Type design analysis — encapsulation, invariant expression, usefulness, and enforcement.

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

Use when you've fixed a bug, added a feature, or made any user-facing change in a project that uses Towncrier and need to record it for the changelog — before committing or opening a PR, or whenever asked to add a changelog entry, towncrier fragment, or news fragment.

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

Turns a single feature idea, improvement, or bug into ONE well-structured GitHub issue. TRIGGER when: the user wants to file/open/create an issue, turn a feature idea or improvement into a ticket, or capture something missing or broken as a ticket. DO NOT TRIGGER when: breaking work into multiple issues or planning a body of work → a planning skill; writing a full Product Requirements Document → creating-prd; the idea is still fuzzy and unhardened → grilling-ideas first.

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

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

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

Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync.

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

Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.

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