Skip to main content
Manusで任意のスキルを実行
ワンクリックで
Rugal
GitHub クリエイタープロフィール

Rugal

1 件の GitHub リポジトリにある 5 件の収集済み skills をリポジトリ単位で表示します。

収集済み skills
5
リポジトリ
1
更新
2026-04-27
リポジトリマップ

skills がある場所

収集済み skill 数が多いリポジトリを、このクリエイターカタログ内の比率と職業範囲とともに表示します。

リポジトリエクスプローラー

リポジトリと代表的な skills

spec-context-checkpoint
一般事務員

保存当前窗口的所有对话记录。保存后建议新开窗口 Resume。 触发时机:用户请求保存、重要节点、长对话。

2026-04-27
spec-context-resume
ソフトウェア開発者

恢复功能的开发上下文。 加载最近会话完整内容 + 历史摘要。

2026-04-27
spec-reflect
ソフトウェア開発者

Extract and persist project knowledge from spec-workflow conversations. Scans user-AI dialogues for coding conventions, architecture decisions, and project patterns, then writes them back to steering documents or conventions directory. Use when (1) a spec-workflow phase completes and new learnings are detected, (2) the user wants to update project conventions, (3) the user says "remember" to persist a specific convention, or (4) the user wants to review and consolidate knowledge from recent features. Triggers include "spec-reflect", "learn conventions", "update conventions", "remember:", "学习规范", "更新规范", "总结回写", "记住这个约定".

2026-04-27
spec-workflow-code-review
ソフトウェア品質保証アナリスト・テスター

Perform comprehensive code review for features developed through the spec-workflow process. Use when all implementation tasks are completed and the user wants to review code quality before generating unit tests or merging. Triggers include "code review for {feature}", "review code", "检查代码", "代码审查", "spec review", or when spec-run's All Tasks Complete Flow offers the code review option. Also use when the user asks to fix review issues, re-review after fixes, or wants to understand the quality of their spec-workflow implementation. This skill integrates with spec-workflow as a post-implementation quality gate — think of it as having a senior engineer review your feature branch before it goes anywhere.

2026-04-27
spec-workflow
ソフトウェア開発者

This skill provides a spec-driven development workflow for systematic feature implementation with validation at each stage. Use when the user wants to (1) initialize a project with steering documents, (2) create feature specifications (requirements, design, tasks), (3) validate specification documents (requirements, design, tasks), (4) execute implementation tasks, (5) generate unit tests for a completed feature, (6) review code for a completed feature, (7) create/analyze/fix/verify bugs, (8) asks about spec-driven development workflow, (9) extract and persist project knowledge from conversations, (10) save/checkpoint conversation context for a feature, or (11) resume/restore conversation context for a feature. Triggers include "create spec", "create requirements/design/tasks", "initialize project", "initialize module", "validate requirements/design/tasks", "execute task", "generate tests", "create unit tests", "code review", "review code", "检查代码", "代码审查", "spec-reflect", "learn conventions", "update conventi

2026-04-27
1 件中 1 件のリポジトリを表示
すべてのリポジトリを表示しました