Use this skill whenever you learn something important during a conversation: a key architectural decision, a project-specific convention, a bug root-cause, a 3rd-party API quirk, or any fact that would help a future agent avoid re-doing the same research. Writes structured entries to the project's knowledge base so that context persists across conversations and agents.
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Activate this skill when any of the following occur:
Choose the category that best describes what was learned:
| Type | When to Use |
|---|---|
decision | Architecture, tech choices, trade-offs |
convention | Naming rules, code patterns, folder structures |
bug | Root cause + fix for a non-obvious problem |
gotcha | 3rd-party quirk, env issue, edge case trap |
research | Answer to a question requiring significant investigation |
Write to: .agent/knowledge/<slug>.md
slug = kebab-case summary of the topic (e.g., auth-token-refresh-strategy).agent/knowledge/auth/, .agent/knowledge/infra/, etc.Use this exact template:
---
type: <decision|convention|bug|gotcha|research>
topic: <Short human-readable title>
date: <YYYY-MM-DD>
tags: [<tag1>, <tag2>]
---
## Summary
<One or two sentences — what was learned, bottom line up front>
## Context
<Why this came up. What problem were we solving?>
## Decision / Finding
<The actual content. Be specific. Include code snippets if helpful.>
## Rationale
<Why this choice over alternatives. What alternatives were rejected and why.>
## Consequences
<What does this affect going forward? What to watch out for?>
## References
- <File path, PR link, conversation snippet, or external URL>
After writing the entry, append a one-line summary to .agent/knowledge/INDEX.md:
| <date> | <type> | [<topic>](./<path>.md) | <one-line summary> |
If INDEX.md doesn't exist yet, create it with this header first:
# Project Knowledge Base
| Date | Type | Topic | Summary |
|------|------|-------|---------|
After writing, report:
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Before committing to an implementation plan, run this skill to stress-test the proposed architecture. Catches over-engineering, circular dependencies, missing failure modes, security gaps, and scalability cliffs — before any code is written. Acts as a "second eye" on the plan.
日本語の概要は準備中です。原文の説明を表示しています。
Systematic code review skill covering both requesting a review (pre-commit checklist) and receiving and responding to review feedback. Checks code quality, security, test coverage, architectural alignment, and documentation before any code is committed.
日本語の概要は準備中です。原文の説明を表示しています。
Periodically scan project dependencies for security vulnerabilities, outdated packages, and unused dependencies. Produces a prioritized action report. Run before every major release and at least once per month.
日本語の概要は準備中です。原文の説明を表示しています。
After any significant code change — new feature, API modification, config change, or architectural refactor — run this skill to identify which documentation files are now stale and update them. Keeps docs and code from drifting apart.
日本語の概要は準備中です。原文の説明を表示しています。
Manages all git operations (commit, push, branch management, PR creation) in a standardized, safe, and consistent way. Automatically runs the code-review skill before any commit. Enforces Conventional Commits standard. Handles the full lifecycle: branch → review → commit → push → PR.
日本語の概要は準備中です。原文の説明を表示しています。
When something breaks in production: triage the severity, gather evidence, identify root cause, deploy a fix or mitigation, and write a post-mortem. Provides a calm, structured process for high-stress moments.
日本語の概要は準備中です。原文の説明を表示しています。