skills.rest
ChanghwanK
ChanghwanKCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

daily:issue-record

Record work issues with status into the '## Issues' section of an Obsidian Daily Note.

Updated Feb 27, 2026
Search Tags:#documentation#task management#issue tracking#obsidian#daily notes#bug logging
One-click install
npx skills add https://github.com/ChanghwanK/dotfiles --skill daily-issue-record
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: daily:issue-record
Source: https://github.com/ChanghwanK/dotfiles/tree/main/claude/.claude/skills/daily%3Aissue-record
Command: npx skills add https://github.com/ChanghwanK/dotfiles --skill daily-issue-record

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of documenting issues encountered during work directly into your Obsidian Daily Notes, ensuring that no problem is lost and providing a clear history of challenges and their resolutions.

Core Features & Use Cases

  • Structured Issue Logging: Records task name, issue details, and resolution status in a predefined format.
  • Daily Note Integration: Appends issues to the ## Issues section of the current day's Obsidian Daily Note.
  • Contextual Awareness: Prompts for missing information if the conversation context is insufficient.
  • Use Case: While working on a complex feature, you encounter a bug. You can immediately use this Skill to log the bug, its description, and mark its status as 'In Progress' within your daily notes without interrupting your flow.

Quick Start

Log the current issue you are facing with the task 'Implement user authentication' and mark its status as 'In Progress'.

Frequently Asked Questions about daily:issue-record

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I log development issues in Obsidian Daily Notes?▼

To log development issues in Obsidian Daily Notes, this Skill appends the task name, issue description, and current status directly to the '## Issues' section of your note, creating the section if it does not exist.

What is the best way to track bug status in Obsidian?▼

Tracking bug status in Obsidian is done by recording the task name, detailed issue description, and current state like 'In Progress' or 'Resolved' into a structured '## Issues' section within your daily notes.

Can I append new issues to an existing Issues section in my daily note?▼

Yes, you can append new issues to an existing '## Issues' section in your daily note. If the section is missing, the Skill automatically creates it before adding your structured issue entry.

What information is required to track an issue in Daily Notes?▼

Tracking an issue in Daily Notes requires the task name, a detailed issue description, and the current status. If your conversation context lacks these details, the Skill prompts you for the missing information.

Does this issue tracking method work without interrupting my development flow?▼

Yes, this issue tracking method works without interrupting your development flow by allowing you to immediately log a bug and mark its status as 'In Progress' within your daily notes through a quick prompt.

Related Skills

Explore More Software Engineering Skills→
justinsenseijustinsensei
1

obsidian-logs

Create and format chronological logs in Obsidian with markdown structure.

Community
Advanced
KIM-KYOUNG-OHKIM-KYOUNG-OH

weekly-newsletter

Aggregate Obsidian vault notes into a Markdown newsletter with structured sections.

Community
Advanced
robertbr123robertbr123

linear

Manage Linear projects, teams, issues, and documents via GraphQL API with curl.

Community
Intermediate
aroidoaroido

work-log

Generate structured daily work logs with status tracking and commit history.

Official
Intermediate