122 skills (repositories by opsmill) · sorted by popularity
Opens a pull request, publishing the current branch as a PR. TRIGGER when: the user wants to open a pull request, publish the current branch as a PR, or take the current work through to an open PR. DO NOT TRIGGER when: only committing changes → commit; babysitting CI after the PR is already open → monitoring-pull-requests.
The English summary is being prepared. Showing the original description.
Stress-tests a fuzzy or vague feature idea before any PRD, spec, or ticket is written. TRIGGER when: the user has a fuzzy feature idea — one or two paragraphs, vague on users / scope / success — and wants to harden it, or says "grill / stress-test / pressure-test this idea." DO NOT TRIGGER when: the idea is already turned into a spec or PRD; bug fixes or refactors; the idea is hardened and you are ready to write the PRD → creating-prd.
The English summary is being prepared. Showing the original description.
Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync.
The English summary is being prepared. Showing the original description.
Validate Jira/JPD ticket reference and create a feature branch
The English summary is being prepared. Showing the original description.
Initialize a Git repository with an initial commit
The English summary is being prepared. Showing the original description.
Validate current branch follows feature branch naming conventions
The English summary is being prepared. Showing the original description.
Execute the implementation planning workflow using the plan template to generate design artifacts.
The English summary is being prepared. Showing the original description.
Error handling review — silent failure detection, catch block analysis, error logging.
The English summary is being prepared. Showing the original description.
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
Extract knowledge, guidelines, and ADRs from one or more completed spec directories into the project documentation system.
The English summary is being prepared. Showing the original description.
Watches an open pull request's CI until green and fixes failing checks. TRIGGER when: the user wants to watch a pull request's CI, babysit a PR until it goes green, or fix failing CI checks on an open PR. DO NOT TRIGGER when: opening the PR in the first place → pr; rebasing the branch onto its base → rebase.
The English summary is being prepared. Showing the original description.
Create or update the feature specification from a natural language feature description.
The English summary is being prepared. Showing the original description.
Generate a custom checklist for the current feature based on user requirements.
The English summary is being prepared. Showing the original description.
General code quality review — project guideline compliance, bug detection, code quality analysis.
The English summary is being prepared. Showing the original description.
Code simplification suggestions — clarity, unnecessary complexity, redundant abstractions. Advisory only.
The English summary is being prepared. Showing the original description.
Type design analysis — encapsulation, invariant expression, usefulness, and enforcement.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
Shared in-workflow quality gates for code/PR skills — the gate model, trust tiers, and the three primitives (evidence-before-done, independent judge, anti-gaming). DO NOT TRIGGER directly — referenced by consumer skills via relative path.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
Refresh the managed Spec Kit section in coding agent context file(s)
The English summary is being prepared. Showing the original description.
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.