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

project-logger

스타4

포크0

업데이트2025년 12월 31일 16:35

Manages project progress tracking and maintains a chronological log of completed tasks, decisions, and updates. Use when completing milestones, making architectural decisions, or documenting project evolution. Creates and updates LOG.md file based on CLAUDE.md context.

설치

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

Manus에서 실행

출처

dudusoar

dudusoar/skillOS

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

다운로드

Manus에서 실행

Project Logger

Overview

This skill maintains a structured project log (LOG.md) that tracks progress, completed tasks, decisions, and important updates. It reads CLAUDE.md to understand project context and creates timestamped entries documenting the project's evolution.

When to Use This Skill

Use this skill when:

Completing a significant task or milestone
Making important architectural or technical decisions
Encountering and resolving issues
Adding new features or capabilities
Updating project dependencies or configuration
Need to review project history

Workflow

Step 1: Locate CLAUDE.md

Find and read the project's CLAUDE.md file to understand:

Project name and goals
Current phase and milestones
Technical architecture
Known issues

Default location: ./.claude/CLAUDE.md

Step 2: Determine Log Entry Type

Identify what type of entry to create:

Task Completion:

Feature implemented
Bug fixed
Refactoring completed
Tests added

Decision:

Architectural choice made
Technology/library selected
Design pattern adopted
Convention established

Update:

Dependency upgraded
Configuration changed
Documentation updated
Milestone reached

Issue:

Problem encountered
Workaround applied
Known limitation documented

Step 3: Create or Update LOG.md

Check if LOG.md exists in .claude/ directory:

If LOG.md doesn't exist:

Create it using the template in references/log_template.md
Add project header with name from CLAUDE.md
Create first entry

If LOG.md exists:

Read existing content
Add new entry at the top (reverse chronological order)
Preserve existing entries

Step 4: Format Log Entry

Each entry should include:

## YYYY-MM-DD HH:MM

### [TYPE] Title

**Context:** Brief explanation of why this happened

**What Changed:**
- Specific change 1
- Specific change 2
- Specific change 3

**Impact:**
- How this affects the project
- Any breaking changes
- Follow-up actions needed

**Related:**
- Links to commits, PRs, or issues (if applicable)
- References to relevant files or documentation

Entry Types:

[FEAT] - New feature
[FIX] - Bug fix
[DECISION] - Architectural/technical decision
[REFACTOR] - Code refactoring
[DOCS] - Documentation update
[DEPS] - Dependency update
[CONFIG] - Configuration change
[MILESTONE] - Milestone reached
[ISSUE] - Problem or limitation

Step 5: Add Entry Example

Good entry:

## 2025-12-30 15:30

### [FEAT] Added skill-analyzer meta-skill

**Context:** Need automated skill selection when starting projects. Manual skill
discovery is time-consuming and error-prone.

**What Changed:**
- Created skill-analyzer meta-skill in `.claude/skills/`
- Implemented workflow to scan SkillOS library
- Added skill matching heuristics based on project context
- Updates CLAUDE.md sections 5 (Available Skills) and 6 (Missing Skills)

**Impact:**
- Automates skill selection for new projects
- Identifies gaps requiring project-specific skills
- Completes the project setup workflow (works with project-context-generator)

**Related:**
- Commit: b27c2ea
- Files: `.claude/skills/skill-analyzer/SKILL.md`

Avoid vague entries:

## 2025-12-30

Updated some files.

Step 6: Update Maintenance Notes in CLAUDE.md

After logging, optionally update the "Maintenance Notes" section in CLAUDE.md:

Update "Last Updated" date
Add entry to "Recent Changes"
Update "Known Issues" if relevant

Log Organization

Reverse Chronological Order

Most recent entries appear first:

# Project Log: SkillOS

## 2025-12-30 16:00
[Most recent]

## 2025-12-30 14:00

## 2025-12-29 10:00
[Oldest at bottom]

Grouping by Date

For multiple entries on the same day, use subheadings:

## 2025-12-30

### 16:00 - [FEAT] Added feature X
...

### 14:00 - [FIX] Fixed bug Y
...

Best Practices

Be Specific

Include file paths, function names, or specific components
Mention exact version numbers for dependencies
Reference commits, PRs, or issues

Explain "Why"

Document the rationale behind decisions
Explain trade-offs considered
Note what alternatives were rejected

Track Impact

Note what breaks (breaking changes)
Identify follow-up work needed
Update known issues

Regular Updates

Log after completing significant work
Don't batch too many changes into one entry
Update while details are fresh

Example LOG.md Structure

See references/log_template.md for the complete template and examples.

Resources

references/log_template.md

Template for creating LOG.md files with:

Header structure
Entry format examples
Best practices
Sample entries for different types

이 저장소의 다른 Skills

같은 저장소

error-logger

dudusoar/skillOS

Maintains detailed log of errors, bugs, and debugging sessions encountered during development. Use when encountering errors, debugging issues, or solving technical problems. Creates structured ERROR_LOG.md with error details, root causes, solutions, and prevention strategies. Complements project-logger (strategic decisions) with tactical debugging knowledge.

2025-12-314

knowledge-extractor

dudusoar/skillOS

Analyzes completed projects to identify generalizable patterns, common workflows, and reusable knowledge worth extracting into skills. Use after completing a project to review LOG.md, skill updates, and project artifacts. Generates extraction recommendations but does not modify skills directly (user decides whether to apply via skill-updater).

2025-12-314

project-context-generator

dudusoar/skillOS

Transforms user project requirements into a structured CLAUDE.md context file. Use when starting a new project and need to document project goals, architecture, technical stack, constraints, and conventions. This skill creates the foundational project context file that other skills and agents will reference throughout the project lifecycle.

2025-12-314

skill-contract-generator

dudusoar/skillOS

Generates evolution contracts for skills, defining what can be updated, what must remain stable, and how to extract knowledge. Use when creating new skills or formalizing update rules for existing skills. Adds a "Skill Contract" section to SKILL.md that guides skill-updater during project work.

2025-12-314

skill-updater

dudusoar/skillOS

Updates skills during project work according to their contracts. Adds references, improves explanations, and refines examples while respecting skill boundaries. Use when discovering patterns, encountering edge cases, or finding better ways to explain skill concepts. Works with skills that have Skill Contracts defined by skill-contract-generator.

2025-12-314

test-writer

dudusoar/skillOS

Generates comprehensive test files for functions and classes. Use after writing a function, method, or class to quickly create unit tests with edge cases, assertions, and proper test structure. Supports multiple testing frameworks (pytest, unittest, jest, etc.) and follows testing best practices (AAA pattern, mocking, fixtures).

2025-12-314

name	project-logger
description	Manages project progress tracking and maintains a chronological log of completed tasks, decisions, and updates. Use when completing milestones, making architectural decisions, or documenting project evolution. Creates and updates LOG.md file based on CLAUDE.md context.