원클릭으로 Manus에서 모든 스킬 실행

template-upstream

스타14

포크0

업데이트2026년 3월 7일 07:03

IMPORTANT: This skill must be run in the template repo context, not in a downstream project. Propose changes from the current project back to the upstream python-project-template repository by generating a structured proposal file in proposals/. Use when a pattern, rule, hook, skill, or config in this project is good enough to share with the template. Triggers on: "템플릿에 반영", "upstream 제안", "template에 올리고 싶어", "이 패턴 템플릿에 추가", "proposal 만들어줘".

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

tae0y

tae0y/python-project-template

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

name: template-upstream description: IMPORTANT: This skill must be run in the template repo context, not in a downstream project. Propose changes from the current project back to the upstream python-project-template repository by generating a structured proposal file in proposals/. Use when a pattern, rule, hook, skill, or config in this project is good enough to share with the template. Triggers on: "템플릿에 반영", "upstream 제안", "template에 올리고 싶어", "이 패턴 템플릿에 추가", "proposal 만들어줘".

template-upstream

Context: Run this skill from the template repo (python-project-template), not from a downstream project. Proposals are template-level artifacts — one shared proposals/ directory for all projects, not one per downstream project.

Direction: Project → Template. Generate a structured proposal file in proposals/ so that good patterns discovered in this project can be reviewed for inclusion in the upstream template.

Proposal File Convention

Path: proposals/draft/YYYYMMDD/proposal-<slug>.md

draft/: all new proposals start here
YYYYMMDD: today's date
slug: kebab-case summary of the change (e.g., add-ruff-hook, update-commit-convention)

Example: proposals/draft/20260222/proposal-add-ruff-hook.md

Proposal File Format

# Proposal: <title>

**Date:** YYYY-MM-DD
**Source project:** <project name from git remote origin or directory name>
**Category:** <rule | hook | skill | config | command | other>
**Status:** draft

## Summary

One paragraph: what is being proposed and why it is useful.

## Motivation

What problem this pattern solved in the source project.
Why it belongs in the template.

### Evidence from localdocs

Cite specific artifacts that demonstrate the pattern has real-world value.
At least one citation required; proposal without evidence is weak.

| Artifact | Location | What it shows |
|----------|----------|---------------|
| learn file | `localdocs/learn.<topic>.md` | Problem encountered, pattern adopted |
| ADR | `localdocs/adr/adr-NNN-<slug>.md` | Architectural decision it supports |
| worklog entry | `localdocs/worklog.done.md` | Task where the pattern made a difference |

If no localdocs evidence exists, state: "No localdocs evidence — pattern is theoretical."
The reviewer (template-proposal-review) will weight this accordingly.

## Proposed Change

### Target path(s) in template

List of file paths to add or modify (relative to template repo root).

### Content

\`\`\`
Full file content or unified diff
\`\`\`

## Caveats

Any considerations when applying. Write "None." if not applicable.

## Review checklist

- [ ] No conflict with existing template files
- [ ] All project-specific values removed (paths, domains, secrets)
- [ ] Downstream sync test needed after applying via template-downstream
- [ ] localdocs evidence cited (or absence explicitly noted)

Steps

1. Clarify scope and load localdocs context

If the user has not specified what to propose, ask:

What would you like to propose to the template?
Please provide a file path or describe the pattern.

Before reading the source file, read the project's localdocs/ to surface evidence:

# Glob for all localdocs artifacts
localdocs/worklog.done.md
localdocs/learn.*.md
localdocs/adr/*.md

Scan these files for mentions of the proposed pattern, file name, or related concepts. The goal is to find real-world evidence that the pattern was applied and produced value — mirroring how the .claude/ review team (review-20260222.md) validated patterns by cross-referencing learn files, ADRs, and worklog entries before recommending promotion.

If localdocs/ does not exist or is empty, note that no evidence is available.

2. Read source file and security review

Read the target file. Before including any content in the proposal, remove or replace the following:

Check	Example	Replace with
API keys / tokens	`sk-...`, `ghp_...`	`<YOUR_API_KEY>`
DDNS / real domains	`myhouse.duckdns.org`	`example.com`
Internal IP addresses	`192.168.1.10`	`<HOST_IP>`
Inlined `.env` values	`password=secret123`	`<YOUR_PASSWORD>`
Absolute paths (home dir)	`/Users/john/projects/`	`<PROJECT_ROOT>/`

After removal, verify the content would be safe to paste into a public GitHub issue.

3. Resolve template root and create date directory

Resolve TEMPLATE_ROOT using the same priority order as template-downstream:

User-provided path — ask the user: "Do you have a local clone of the template repo? If yes, provide the path." If provided and <path>/.claude/ exists, use its parent as TEMPLATE_ROOT.
Clone — otherwise:

TMPDIR=$(mktemp -d)
git clone --depth 1 https://github.com/tae0y/python-project-template.git "$TMPDIR/template"
TEMPLATE_ROOT="$TMPDIR/template"

Then create the proposals directory:

mkdir -p "$TEMPLATE_ROOT/proposals/draft/YYYYMMDD"

Skip if already exists.

4. Write proposal file

Create $TEMPLATE_ROOT/proposals/draft/YYYYMMDD/proposal-<slug>.md using the format above.

Replace all project-specific values with <your-value> placeholders
Infer Category from file location: .claude/rules/ → rule, .claude/hooks/ → hook, .claude/skills/ → skill, etc.

5. Report

Created: <TEMPLATE_ROOT>/proposals/draft/20260222/proposal-<slug>.md

Review and apply via the template-proposal-review skill.

이 저장소의 다른 Skills

같은 저장소

template-broadcast

tae0y/python-project-template

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".

2026-07-2514

voice-business

tae0y/python-project-template

The standard business voice for any Korean text a human reads — a formal-yet-friendly business register built on 해요체 but elevated with 합니다/습니다 endings, polite recommendation phrasing, natural greetings/closings, and readable structure. Use whenever producing or rewriting reader-facing text: Telegram replies, reports, READMEs, job outputs, human-facing notes, and especially when rewriting raw TIL/technical notes for sharing with colleagues. Triggers: 비즈니스 톤, business voice, 격식 있는 톤, 동료 공유용 재작성, formal rewrite, 보고서 톤, 발표자료 톤.

2026-07-1814

k-skill

tae0y/python-project-template

한국 특화 기능(교통·날씨·부동산·쇼핑·법률·금융·공공데이터 등) 요청이 들어오면 실행. git pull로 최신화 후 README 레지스트리에서 스킬을 골라 해당 SKILL.md만 읽어 진행한다.

2026-05-1314

sentinel-import

tae0y/python-project-template

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에서 배운 것", "실패 경험 가져와".

2026-05-1314

template-downstream

tae0y/python-project-template

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 업데이트".

2026-05-1314

planning

tae0y/python-project-template

Planning work in small, known-good increments. Use when starting significant work or breaking down complex tasks.

2026-05-1014

name: template-upstream description: IMPORTANT: This skill must be run in the template repo context, not in a downstream project. Propose changes from the current project back to the upstream python-project-template repository by generating a structured proposal file in proposals/. Use when a pattern, rule, hook, skill, or config in this project is good enough to share with the template. Triggers on: "템플릿에 반영", "upstream 제안", "template에 올리고 싶어", "이 패턴 템플릿에 추가", "proposal 만들어줘".

template-upstream

Context: Run this skill from the template repo (python-project-template), not from a downstream project. Proposals are template-level artifacts — one shared proposals/ directory for all projects, not one per downstream project.

Direction: Project → Template. Generate a structured proposal file in proposals/ so that good patterns discovered in this project can be reviewed for inclusion in the upstream template.

Proposal File Convention

Path: proposals/draft/YYYYMMDD/proposal-<slug>.md

draft/: all new proposals start here
YYYYMMDD: today's date
slug: kebab-case summary of the change (e.g., add-ruff-hook, update-commit-convention)

Example: proposals/draft/20260222/proposal-add-ruff-hook.md

Proposal File Format

# Proposal: <title>

**Date:** YYYY-MM-DD
**Source project:** <project name from git remote origin or directory name>
**Category:** <rule | hook | skill | config | command | other>
**Status:** draft

## Summary

One paragraph: what is being proposed and why it is useful.

## Motivation

What problem this pattern solved in the source project.
Why it belongs in the template.

### Evidence from localdocs

Cite specific artifacts that demonstrate the pattern has real-world value.
At least one citation required; proposal without evidence is weak.

| Artifact | Location | What it shows |
|----------|----------|---------------|
| learn file | `localdocs/learn.<topic>.md` | Problem encountered, pattern adopted |
| ADR | `localdocs/adr/adr-NNN-<slug>.md` | Architectural decision it supports |
| worklog entry | `localdocs/worklog.done.md` | Task where the pattern made a difference |

If no localdocs evidence exists, state: "No localdocs evidence — pattern is theoretical."
The reviewer (template-proposal-review) will weight this accordingly.

## Proposed Change

### Target path(s) in template

List of file paths to add or modify (relative to template repo root).

### Content

\`\`\`
Full file content or unified diff
\`\`\`

## Caveats

Any considerations when applying. Write "None." if not applicable.

## Review checklist

- [ ] No conflict with existing template files
- [ ] All project-specific values removed (paths, domains, secrets)
- [ ] Downstream sync test needed after applying via template-downstream
- [ ] localdocs evidence cited (or absence explicitly noted)

Steps

1. Clarify scope and load localdocs context

If the user has not specified what to propose, ask:

What would you like to propose to the template?
Please provide a file path or describe the pattern.

Before reading the source file, read the project's localdocs/ to surface evidence:

# Glob for all localdocs artifacts
localdocs/worklog.done.md
localdocs/learn.*.md
localdocs/adr/*.md

If localdocs/ does not exist or is empty, note that no evidence is available.

2. Read source file and security review

Read the target file. Before including any content in the proposal, remove or replace the following:

Check	Example	Replace with
API keys / tokens	`sk-...`, `ghp_...`	`<YOUR_API_KEY>`
DDNS / real domains	`myhouse.duckdns.org`	`example.com`
Internal IP addresses	`192.168.1.10`	`<HOST_IP>`
Inlined `.env` values	`password=secret123`	`<YOUR_PASSWORD>`
Absolute paths (home dir)	`/Users/john/projects/`	`<PROJECT_ROOT>/`

After removal, verify the content would be safe to paste into a public GitHub issue.

3. Resolve template root and create date directory

Resolve TEMPLATE_ROOT using the same priority order as template-downstream:

User-provided path — ask the user: "Do you have a local clone of the template repo? If yes, provide the path." If provided and <path>/.claude/ exists, use its parent as TEMPLATE_ROOT.
Clone — otherwise:

TMPDIR=$(mktemp -d)
git clone --depth 1 https://github.com/tae0y/python-project-template.git "$TMPDIR/template"
TEMPLATE_ROOT="$TMPDIR/template"

Then create the proposals directory:

mkdir -p "$TEMPLATE_ROOT/proposals/draft/YYYYMMDD"

Skip if already exists.

4. Write proposal file

Create $TEMPLATE_ROOT/proposals/draft/YYYYMMDD/proposal-<slug>.md using the format above.

Replace all project-specific values with <your-value> placeholders
Infer Category from file location: .claude/rules/ → rule, .claude/hooks/ → hook, .claude/skills/ → skill, etc.

5. Report

Created: <TEMPLATE_ROOT>/proposals/draft/20260222/proposal-<slug>.md

Review and apply via the template-proposal-review skill.