sentinel-import
Import Dev Sentinel experiences into localdocs/learn.sentinel.md. Use when the user wants to bring gotchas, failure lessons, or struggle experiences captured by Dev Sentinel into the project's local knowledge base. Triggers: "sentinel 가져와", "sentinel import", "gotcha 정리", "경험 가져와", "sentinel에서 배운 것", "실패 경험 가져와".
Best use case
sentinel-import is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Import Dev Sentinel experiences into localdocs/learn.sentinel.md. Use when the user wants to bring gotchas, failure lessons, or struggle experiences captured by Dev Sentinel into the project's local knowledge base. Triggers: "sentinel 가져와", "sentinel import", "gotcha 정리", "경험 가져와", "sentinel에서 배운 것", "실패 경험 가져와".
Teams using sentinel-import should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/sentinel-import/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How sentinel-import Compares
| Feature / Agent | sentinel-import | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Import Dev Sentinel experiences into localdocs/learn.sentinel.md. Use when the user wants to bring gotchas, failure lessons, or struggle experiences captured by Dev Sentinel into the project's local knowledge base. Triggers: "sentinel 가져와", "sentinel import", "gotcha 정리", "경험 가져와", "sentinel에서 배운 것", "실패 경험 가져와".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Sentinel Import Import confirmed experiences from Dev Sentinel CLI into `localdocs/learn.sentinel.md`. ## Workflow ### 1. Check Sentinel availability ```bash which sentinel 2>/dev/null && sentinel status ``` If `sentinel` is not found, guide installation and stop: ``` Dev Sentinel CLI가 설치되어 있지 않아요. 설치 방법: 1. 소스 클론 (이미 있다면 건너뛰기): git clone https://github.com/elbanic/dev-sentinel.git 2. 빌드 및 글로벌 설치: cd dev-sentinel npm install && npm link 3. Ollama 모델 준비: ollama pull qwen3:4b ollama pull qwen3-embedding:0.6b 4. 이 프로젝트에서 초기화: cd <project-root> sentinel init 설치 후 다시 "sentinel 가져와"를 실행해주세요. ``` If sentinel is available but status shows 0 experiences and 0 drafts, inform user and stop. ### 2. Handle pending drafts first ```bash sentinel review list ``` If pending drafts exist, ask user whether to confirm them first: - `sentinel review confirm --all` to confirm all - `sentinel review confirm --recent` to confirm latest only - Skip to import only already-confirmed experiences Confirming triggers LLM summarization (requires Ollama running). ### 3. List confirmed experiences ```bash sentinel list ``` Show the list to the user. Ask which to import: - All experiences - Specific IDs - Only new ones (not already in learn.sentinel.md) ### 4. Fetch detail for each selected experience ```bash sentinel detail <id> ``` Capture these fields: - **Issue** (frustrationSignature) - **Failed Approaches** (what didn't work) - **Successful Approach** (what solved it) - **Lessons** (key takeaways) ### 5. Write to localdocs/learn.sentinel.md Append each experience under a dated section. Follow this format: ```markdown ## YYYY-MM-DD ### <Issue title — concise, one line> **ID:** `<sentinel-experience-id>` **Failed approaches:** - <approach 1> - <approach 2> **Solution:** <successful approach> **Lessons:** - <lesson 1> - <lesson 2> ``` Rules: - Create the file if it doesn't exist, with `# Sentinel Experiences` as heading - Check existing content to avoid duplicating IDs already imported - Append new experiences under today's date section - Keep original Sentinel ID for traceability ### 6. Report result ``` Imported N experience(s) to localdocs/learn.sentinel.md Skipped M already-imported experience(s) ```
Related Skills
worklog
Update worklog files by moving tasks between todo/doing/done states. Use when recording task progress, starting new work, or marking tasks complete. Requires explicit arguments: worklog [done|doing|todo] [description].
template-proposal-review
Review proposal files in localdocs/localdocs/proposals/ and decide whether to apply them to the upstream python-project-template repository. Use when evaluating proposals generated by template-upstream, deciding which ones to accept or reject, and applying accepted ones to the template repo. Triggers on: "proposal 검토", "제안 검토", "template에 반영할지", "proposals 리뷰", "upstream 반영 결정".
template-downstream
Update .claude/, .mcp.json, and .pre-commit-config.yaml from the upstream python-project-template repository into the current project. Only files that exist upstream are updated — project-only files are never deleted. Use when pulling latest tooling, rules, hooks, or skills from the canonical template into this project. Triggers on: "템플릿 최신화", "template sync", "upstream 반영", "template 업데이트".
template-broadcast
Apply template-downstream to all registered downstream projects in bulk, one project at a time. Use when you want to push the latest .claude/, .mcp.json, or .pre-commit-config.yaml to every project at once. Triggers on: "일괄 배포", "전체 프로젝트에 내려보내기", "모든 프로젝트 업데이트", "broadcast template", "bulk sync".
tdd
Test-Driven Development workflow. Use for ALL code changes - features, bug fixes, refactoring. TDD is non-negotiable.
sparks-create
Apply the 13 thinking tools from "Sparks of Genius" (생각의 탄생) to reframe any problem through creative, cross-disciplinary lenses. Use when conventional analysis falls short, when you need a fresh creative angle, or when the problem spans multiple domains.
skill-creator
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
rethink-unblock
Break out of a stuck approach by reframing a technical problem through structured thinking frameworks. Use when blocked, going in circles, or when a fresh perspective is needed on architecture, design, or debugging.
refactoring
Refactoring assessment and patterns. Use after tests pass (GREEN phase) to assess improvement opportunities.
python-mcp-expert
Expert assistant for developing Model Context Protocol (MCP) servers in Python. Use when creating, debugging, or optimizing MCP servers with FastMCP, tools, resources, and prompts.
python-conventions
Python coding conventions and guidelines including PEP 8, type hints, docstrings, and testing standards. Automatically applied when working with Python files.
prd
Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.