From obsidian
Generates team work logs from git context (logs, diffs, status, PRs) and 3 focused questions, then pushes Markdown files to shared GitHub repo via gh CLI for weekly reviews.
npx claudepluginhub orange-brother/obsidian-skills --plugin obsidianThis skill uses the workspace's default tool permissions.
Turn a completed task into a team-facing work log and push it to the team's shared GitHub repository using `gh` CLI. Designed for weekly review — concise, factual, and easy to scan.
Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.
Processes PDFs: extracts text/tables/images, merges/splits/rotates pages, adds watermarks, creates/fills forms, encrypts/decrypts, OCRs scans. Activates on PDF mentions or output requests.
Share bugs, ideas, or general feedback.
Turn a completed task into a team-facing work log and push it to the team's shared GitHub repository using gh CLI. Designed for weekly review — concise, factual, and easy to scan.
TEAM_REPO = the-swing/fe-work-logs
TEAM_REPO: GitHub repository in org/repo format{git user.name}/{YYYY-MM-DD}-{task-name}.mdgh CLI must be installed and authenticated (gh auth status)Check if TEAM_REPO is still set to the placeholder value the-swing/fe-work-logs.
If it is:
If TEAM_REPO is already configured, skip this step silently.
The user provides:
If missing, ask for it before proceeding.
Without asking the user, run:
git config user.name
git config user.email
git log --oneline -10
git diff HEAD~1 HEAD --stat
git status
gh pr view
Extract:
git config user.namegh pr view if availableDo not ask the user about things you can derive from git.
Ask exactly 3 questions, all at once:
Use the obsidian-markdown skill for structure — frontmatter and headings.
Use the human-writer skill for all prose content within each section. Apply its vocabulary, structural, and voice rules to every sentence written. The text should sound like the user wrote it, not like an AI summarized it.
Generate the markdown file and upload to the team repo via gh CLI:
# Write to temp file
cat > /tmp/team-log-output.md << 'EOF'
{file content}
EOF
# Upload to team repo
AUTHOR=$(git config user.name)
FILE_PATH="$AUTHOR/{YYYY-MM-DD}-{task-name}.md"
SHA=$(gh api repos/{TEAM_REPO}/contents/$FILE_PATH --jq '.sha' 2>/dev/null)
gh api repos/{TEAM_REPO}/contents/$FILE_PATH \
--method PUT \
-f message="team-log: {task-name}" \
-f content="$(base64 -i /tmp/team-log-output.md)" \
${SHA:+-f sha="$SHA"}
# Clean up
rm /tmp/team-log-output.md
---
title: {Task Name}
date: {YYYY-MM-DD}
author: {git user.name}
tags:
- team-log
status: done
---
# {Task Name}
| 항목 | 내용 |
|------|------|
| 작업자 | {git user.name} |
| 날짜 | {YYYY-MM-DD} |
| PR | {PR link or 없음} |
## 작업 내용
{변경된 파일과 커밋 요약. 짧은 bullet list.}
## 고민한 흔적
{핵심 결정 이유와 어려웠던 점. 1인칭으로, 2~4문장.}
## 영향 범위 및 팀 공유
{팀원이 알아야 할 것. 없으면 "없음".}
## 다음 액션
{이어질 작업이나 블로커. 없으면 생략.}
You MUST write the entire log in Korean, regardless of the language the user used. Keep it concise — this is a team scan document, not a personal retrospective.