CtrlK
BlogDocsLog inGet started
Tessl Logo

load-issues

Load all open issues from GitHub and save them as markdown files

67

Quality

61%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/git/skills/load-issues/SKILL.md
SKILL.md
Quality
Evals
Security

Load all open issues from the current GitHub repository and save them as markdown files in the ./specs/issues/ directory.

Follow these steps:

  1. Use the gh CLI to list all open issues in the current repository:

    • Run gh issue list --limit 100 to get all open issues
  2. For each open issue, fetch detailed information:

    • Run gh issue view <number> --json number,title,body,state,createdAt,updatedAt,author,labels,assignees,url
    • Extract all relevant metadata
  3. Create the issues directory:

    • Run mkdir -p ./specs/issues to ensure the directory exists
  4. Save each issue as a separate markdown file:

    • File naming pattern: <number-padded-to-3-digits>-<kebab-case-title>.md
    • Example: 007-make-code-review-trigger-on-sql-sh-changes.md
  5. Use the following markdown template for each issue file:

# Issue #<number>: <title>

**Status:** <state>
**Created:** <createdAt>
**Updated:** <updatedAt>
**Author:** <author.name> (@<author.login>)
**URL:** <url>

## Description

<body>

## Labels

<labels or "None">

## Assignees

<assignees or "None">
  1. After all issues are saved, provide a summary of:
    • Total number of issues loaded
    • List of created files with their issue numbers and titles

IMPORTANT: Execute all steps in the correct order and ensure all issue data is properly formatted in the markdown files.

Repository
NeoLabHQ/context-engineering-kit
Last updated
Created

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.