update-learning-logs

showdaiya's avatarfrom showdaiya

Update the project learning logs (PowerShell/cmd, Git/GitHub/Copilot, AWS, TypeScript, Next.js/React, Playwright) by merging new knowledge into existing categories across one or more files.

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 3, 2026⬇️1downloads
[Knowledge Base]

When & Why to Use This Skill

This Claude skill automates the maintenance of technical documentation by intelligently merging new insights into existing project learning logs. It ensures that knowledge regarding PowerShell, Git, AWS, TypeScript, and Playwright remains organized by topic rather than date, preventing information silos and duplicate entries while keeping documentation searchable and up-to-date.

Use Cases

  • Technical Debt Reduction: Automatically consolidating scattered notes on PowerShell or CMD commands into a single, structured reference file.
  • Developer Onboarding: Maintaining a clean, topic-based knowledge base for TypeScript and React patterns to help new team members understand project standards.
  • Infrastructure Documentation: Merging new AWS CLI operations and IAM policy learnings into existing logs to ensure cloud infrastructure knowledge is preserved.
  • Testing Best Practices: Updating Playwright testing guides with newly discovered debugging steps and configuration tweaks directly after a testing session.
  • Automated Documentation Workflow: Streamlining the process of staging, committing, and pushing documentation updates to GitHub with clear, descriptive commit messages.
nameupdate-learning-logs
descriptionUpdate the project learning logs (PowerShell/cmd, Git/GitHub/Copilot, AWS, TypeScript, Next.js/React, Playwright) by merging new knowledge into existing categories across one or more files.

Goal

Keep learning notes searchable by topic (not by date) and continuously improved via merge updates (統合アップデート) instead of duplicating entries.

When to use

Use this skill when:

  • We executed or discussed PowerShell/cmd commands.
  • We executed or discussed Git/GitHub operations (branches, PRs, Actions, Copilot, MCP).
  • We executed or discussed AWS operations (S3/CloudFront/OAC/IAM/AWS CLI).
  • We implemented or discussed TypeScript / Next.js / React topics.
  • We added or modified Playwright tests, configuration, or debugging steps.

Target files (choose one or more)

Topic File
PowerShell/cmd docs/command-learning-log.md
Git/GitHub/Copilot/MCP docs/git-github-learning-log.md
AWS docs/aws-learning-log.md
TypeScript docs/typescript-learning-log.md
Next.js/React docs/nextjs-learning-log.md
Playwright docs/playwright-learning-log.md

Process (multi-file aware)

  1. Collect new learnings from the current work (commands used, concepts explained, errors encountered, decisions made).
  2. Decide target logs (one or multiple files) based on topic.
  3. For each target file:
    • Locate the existing best-matching category section.
    • Merge-update the existing entry:
      • Prefer adding missing sections (基礎/関連/応用/トラブル) over creating a new duplicate entry.
      • If there are duplicates, consolidate into one canonical section and keep the best wording/examples.
      • Keep headings stable so future updates land in the same place.
    • Add a short 学んだ日: YYYY-MM-DD line when new knowledge was added.
  4. Show the proposed diffs (file list + what changed) and ask for confirmation if committing.
  5. If the user requests commit/push:
    • Stage only the learning-log related files (avoid accidental staging of generated artifacts like playwright-report/, test-results/, etc.).
    • Provide a clear commit message (e.g., docs: update learning logs (git/github + playwright)), then push.

Output checklist

  • Which log files were updated (may be multiple)
  • What knowledge was added (bullets)
  • Any risky commands/topics called out
  • VERIFY commands to re-check
  • Rollback steps (how to revert)