kiln-report-issue

Create timestamped issue entries in the .kiln/issues/ directory.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/yoshisada/ai-repo-template --skill kiln-report-issue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kiln-report-issue
Source: https://github.com/yoshisada/ai-repo-template/tree/main/plugin-kiln/skills/kiln-report-issue
Command: npx skills add https://github.com/yoshisada/ai-repo-template --skill kiln-report-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture and persist bugs, friction points, or improvement ideas by creating timestamped entries in the project's backlog (.kiln/issues/), ensuring nothing gets forgotten.

Core Features & Use Cases

  • Create timestamped backlog entries from natural language descriptions.
  • Auto-detect repository context and optionally attach the source repo URL.
  • Integrate with Obsidian shelf to sync issues for quick reference and tracking.

Quick Start

Describe the issue and run the kiln-report-issue command to create a timestamped backlog entry.

Frequently Asked Questions about kiln-report-issue

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

FAQPage Schema
How do I log issues to a backlog from Obsidian?

You can log issues from Obsidian by describing the bug or improvement idea and running the command to create a timestamped entry in the .kiln/issues/ directory, ensuring nothing gets forgotten.

What is the best way to capture bugs and improvement ideas in a local knowledge base?

Capturing bugs and improvement ideas is best handled by creating timestamped backlog entries from natural language descriptions, automatically syncing them for quick reference and tracking.

Does the Kiln backlog integration auto-detect the repository URL?

Yes, the Kiln backlog integration auto-detects the repository context and optionally attaches the source repo URL to the issue entry during the background synchronization process.

Can I extract file paths from natural language issue descriptions?

Yes, you can extract relevant file paths from natural language issue descriptions because the workflow validates input and parses the text to attach contextual file locations to the backlog entry.

Do I need a specific repository setup to sync issues from Obsidian?

You need a collaborative software project using Kiln and Obsidian workflows, as the implementation creates entries in the .kiln/issues/ directory and triggers background synchronization to the backlog.