「smil」の検索結果

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.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

Initialize a Git repository with an initial commit

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

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

日本語の概要は準備中です。原文の説明を表示しています。

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

日本語の概要は準備中です。原文の説明を表示しています。

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

日本語の概要は準備中です。原文の説明を表示しています。

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

日本語の概要は準備中です。原文の説明を表示しています。

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

日本語の概要は準備中です。原文の説明を表示しています。

Code simplification suggestions — clarity, unnecessary complexity, redundant abstractions. Advisory only.

日本語の概要は準備中です。原文の説明を表示しています。

Test coverage quality analysis — behavioral coverage, critical gap identification, test resilience evaluation.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

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

日本語の概要は準備中です。原文の説明を表示しています。

Create or update the feature specification from a natural language feature 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.

日本語の概要は準備中です。原文の説明を表示しています。

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

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

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

日本語の概要は準備中です。原文の説明を表示しています。

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

日本語の概要は準備中です。原文の説明を表示しています。

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

日本語の概要は準備中です。原文の説明を表示しています。

Detect Git remote URL for GitHub integration

日本語の概要は準備中です。原文の説明を表示しています。

Migrate Infrahub docs feature pages from the legacy topic+guide pair into a cleaner structure (single merged page, hub+spokes, or tutorial extraction). Supports both single-feature migrations (one feature like Profiles or Webhooks) and section-wide migrations (a whole section like Branches & Change Control with multiple features migrated together) when the team has agreed on a section-wide restructure plan. Trigger when the user names a specific feature or section to migrate (e.g. "let's migrate profiles", "start the Resource Manager migration", "do the entire Branches & Change Control section"). Each migration is its own branch off `demo/groups-diataxis-example`, its own PR back to that branch.

日本語の概要は準備中です。原文の説明を表示しています。