issues

Name: issues
Author: exentials

Issues Instructions

by exentials(0) 0 installs

Free

Free account. Installing gives you the manifest plus copy-paste snippets.

See reviews

About

Instruction file imported from exentials/OpenMES (.github/instructions/issues.instructions.md). Copyright stays with the author.

Issues Instructions

Mandatory

Create/update ISSUES.md where analysis is done.
Keep one file per logical area/project when possible.

Track categories

Bugs
Bug risks
Architecture flaws
Security issues
Performance risks
Test gaps

Strict format

For each issue use:

ID: ISS-###
Severity: Critical | High | Medium | Low
Priority: P1 | P2 | P3
Area: <project/module>
Problem: <one line>
Fix: <one line>
Reference: <file path + line if possible>

Rules

One issue = one problem.
No vague issue text.
No duplicates.
Keep IDs stable.
New issue increments last number.

Reporting locations

ISSUES.md is source of truth.
Important test gaps also summarized in project README.md testing section.

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

yaml

targets:
  - https://api.opensmartroute.ai/api/v1/registry/exentials-openmes-issues-instructions/manifest   # or paste the manifest below

Manifest

An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.

exentials-openmes-issues-instructions.ocm.jsonjson

{
  "ocm": "1",
  "id": "exentials-openmes-issues-instructions",
  "kind": "skill",
  "name": "issues",
  "description": "Issues Instructions",
  "publisher": "exentials",
  "version": "1.0.0",
  "capabilities": {
    "domains": [
      "general"
    ],
    "tags": [
      "skill-md",
      "github-instructions"
    ],
    "languages": [
      "en"
    ]
  },
  "quality_prior": 0.6,
  "examples": [
    "Issues Instructions"
  ],
  "primary": false,
  "metadata": {
    "source": {
      "provider": "github-instructions",
      "repository": "https://github.com/exentials/OpenMES",
      "path": ".github/instructions/issues.instructions.md",
      "ref": "55c0de6c691299978e154318deee7d42a5ad0226",
      "url": "https://github.com/exentials/OpenMES/blob/55c0de6c691299978e154318deee7d42a5ad0226/.github/instructions/issues.instructions.md",
      "key": "exentials/OpenMES/.github/instructions/issues.instructions.md"
    },
    "applies_to": [
      "**/*"
    ]
  },
  "instructions": "# Issues Instructions\n\n## Mandatory\n- Create/update `ISSUES.md` where analysis is done.\n- Keep one file per logical area/project when possible.\n\n## Track categories\n- Bugs\n- Bug risks\n- Architecture flaws\n- Security issues\n- Performance risks\n- Test gaps\n\n## Strict format\nFor each issue use:\n\n- `ID: ISS-###`\n- `Severity: Critical | High | Medium | Low`\n- `Priority: P1 | P2 | P3`\n- `Area: <project/module>`\n- `Problem: <one line>`\n- `Fix: <one line>`\n- `Reference: <file path + line if possible>`\n\n## Rules\n- One issue = one problem.\n- No vague issue text.\n- No duplicates.\n- Keep IDs stable.\n- New",
  "cost": {
    "context_tokens": 191
  }
}

Fetch it by URL: GET /api/v1/registry/exentials-openmes-issues-instructions/manifest?version=1.0.0

About

Issues Instructions

Mandatory

Track categories

Strict format

Rules

Reporting locations

Use it

Manifest

Reviews