[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MKAMYMZ3NPHPCWR0RYEXZY":3,"skill-same:01M6MKAMYMZ3NPHPCWR0RYEXZY":72},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":48,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":51,"updatedAt":52,"install":53,"resources":65},"01M6MKAMYMZ3NPHPCWR0RYEXZY","skill-issues",null,"Track project blockers, bugs, and gaps across sessions — use when issues pile up or need triage","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fnyldn\u002Fclaude-octopus\u002Fskills\u002Fskill-issues\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36],"issues","skill issues","triage","sessions","use","up","across","project","true","bugs","track","gaps","when","2026-11-10 10:12:30",false,"---\nname: skill-issues\ndescription: \"Track project blockers, bugs, and gaps across sessions — use when issues pile up or need triage\"\ndisable-model-invocation: true\n---\n\n> **Host: Codex CLI** — This skill was designed for Claude Code and adapted for Codex.\n> Cross-reference commands use installed skill names in Codex rather than `\u002Focto:*` slash commands.\n> Use the active Codex shell and subagent tools. Do not claim a provider, model, or host subagent is available until the current session exposes it.\n> For host tool equivalents, see `skills\u002Fblocks\u002Fcodex-host-adapter.md`.\n\n\n# Issue Tracking\n\n## Overview\n\nCross-session issue tracking for persistent problem management. Issues are stored in `.octo\u002FISSUES.md` and survive across Claude Code sessions.\n\n**Core principle:** Track → Resolve → Learn.\n\n\n## When to Use\n\n**Use this skill when user wants to:**\n- Track a problem or blocker for later\n- Record issues discovered during development\n- Review open issues across sessions\n- Mark issues as resolved\n- View details of specific issues\n\n**Do NOT use for:**\n- GitHub issue management (use gh CLI)\n- Git-tracked issues (use git commands)\n- Temporary todos (use task plan tool)\n\n\n## Subcommands\n\n### 1. List Issues (Default)\n\n**Trigger:** `\u002Focto:issues` or `\u002Focto:issues list`\n\nShow all open issues in table format:\n\n```markdown\n## Open Issues\n\n| ID | Severity | Category | Description | Created | Phase |\n|----|----------|----------|-------------|---------|-------|\n| ISS-20260203-001 | high | integration | Auth not working | 2026-02-03 | Develop |\n| ISS-20260203-002 | medium | performance | Slow query performance | 2026-02-03 | Deliver |\n```\n\n**Pattern Detection:** After listing, check if 3+ open issues share the same category. If so, alert:\n```text\n⚠ Pattern detected: 3 open issues in category \"integration\" — may indicate a systemic problem.\n```\n\n**Implementation:**\n1. Check if `.octo\u002FISSUES.md` exists\n2. If not, initialize from template\n3. Read and parse Open Issues section\n4. Display in table format\n\n\n### 2. Add Issue\n\n**Trigger:** `\u002Focto:issues add \u003Cdescription>`\n\nAdd new issue with auto-generated ID.\n\n**Flow:**\n\n#### Step 1: Gather Information\n\nUse AskUserQuestion with two questions:\n\n```javascript\nAskUserQuestion({\n  questions: [\n    {\n      question: \"What severity is this issue?\",\n      header: \"Severity\",\n      multiSelect: false,\n      options: [\n        {label: \"critical\", description: \"Blocks all progress\"},\n        {label: \"high\", description: \"Significant impact\"},\n        {label: \"medium\", description: \"Should address\"},\n        {label: \"low\", description: \"Nice to fix\"}\n      ]\n    },\n    {\n      question: \"What category does this issue fall into?\",\n      header: \"Category\",\n      multiSelect: false,\n      options: [\n        {label: \"logic-error\", description: \"Incorrect behavior or wrong output\"},\n        {label: \"integration\", description: \"Cross-component or API compatibility\"},\n        {label: \"quality-gate\", description: \"Quality gate failures during workflows\"},\n        {label: \"security\", description: \"Security vulnerabilities or concerns\"},\n        {label: \"performance\", description: \"Speed, memory, or scalability issues\"},\n        {label: \"ux\", description: \"User experience or usability problems\"},\n        {label: \"architecture\", description: \"Structural or design pattern issues\"}\n      ]\n    }\n  ]\n})\n```\n\n#### Step 2: Determine Current Phase\n\n```bash\n# Check if STATE.md exists\nif [ -f .octo\u002FSTATE.md ]; then\n  grep \"current_phase:\" .octo\u002FSTATE.md\nelse\n  echo \"Unknown\"\nfi\n```\n\n#### Step 3: Generate Issue ID\n\n**Format:** `ISS-YYYYMMDD-NNN`\n\n```bash\n# Get today's date\nTODAY=$(date +%Y%m%d)\n\n# Find existing issues for today\ngrep \"ISS-${TODAY}-\" .octo\u002FISSUES.md | tail -1\n\n# Increment sequence number\n# If ISS-20260203-001 exists, next is ISS-20260203-002\n```\n\n#### Step 4: Append to ISSUES.md\n\nAdd new row to Open Issues table:\n\n```markdown\n| ISS-20260203-003 | medium | performance | Slow query performance | 2026-02-03 | Develop |\n```\n\n**Preserve existing issues** - append only, don't overwrite.\n\n#### Step 5: Confirm\n\n```markdown\n✅ Issue created: ISS-20260203-003\n\n**Severity:** medium\n**Category:** performance\n**Description:** Slow query performance\n**Created:** 2026-02-03\n**Phase:** Develop\n\nView with: \u002Focto:issues show ISS-20260203-003\n```\n\n\n### 3. Resolve Issue\n\n**Trigger:** `\u002Focto:issues resolve \u003Cid>`\n\nMark issue as resolved and move to Resolved section.\n\n**Flow:**\n\n#### Step 1: Validate Issue Exists\n\n```bash\n# Check if issue ID exists in Open Issues\ngrep \"ISS-20260203-001\" .octo\u002FISSUES.md\n```\n\nIf not found, show error:\n\n```markdown\n❌ Issue ISS-20260203-001 not found in open issues.\n\nUse `\u002Focto:issues list` to see all open issues.\n```\n\n#### Step 2: Ask for Resolution Notes\n\n```markdown\n**Resolving issue:** ISS-20260203-001\n\nPlease provide resolution notes:\n```\n\n#### Step 3: Move to Resolved Section\n\n1. Extract issue row from Open Issues table\n2. Remove from Open Issues\n3. Add to Resolved Issues with resolution date and notes\n\n**Resolved Issues format:**\n\n```markdown\n| ID | Severity | Category | Description | Created | Resolved | Resolution |\n|----|----------|----------|-------------|---------|----------|------------|\n| ISS-20260203-001 | high | integration | Auth not working | 2026-02-03 | 2026-02-04 | Fixed OAuth token refresh |\n```\n\n#### Step 4: Confirm\n\n```markdown\n✅ Issue resolved: ISS-20260203-001\n\n**Resolution date:** 2026-02-04\n**Resolution notes:** Fixed OAuth token refresh\n\nView with: \u002Focto:issues show ISS-20260203-001\n```\n\n\n### 4. Show Issue Details\n\n**Trigger:** `\u002Focto:issues show \u003Cid>`\n\nDisplay full details of specific issue.\n\n**Flow:**\n\n#### Step 1: Find Issue\n\nSearch both Open and Resolved sections for issue ID.\n\n#### Step 2: Display Details\n\n**For open issue:**\n\n```markdown\n## Issue Details: ISS-20260203-001\n\n**Status:** Open\n**Severity:** high\n**Category:** integration\n**Description:** Auth not working\n**Created:** 2026-02-03\n**Phase:** Develop\n\n**Actions:**\n- Resolve: `\u002Focto:issues resolve ISS-20260203-001`\n```\n\n**For resolved issue:**\n\n```markdown\n## Issue Details: ISS-20260203-001\n\n**Status:** Resolved\n**Severity:** high\n**Category:** integration\n**Description:** Auth not working\n**Created:** 2026-02-03\n**Resolved:** 2026-02-04\n**Resolution:** Fixed OAuth token refresh\n```\n\n#### Step 3: If Not Found\n\n```markdown\n❌ Issue ISS-20260203-001 not found.\n\nUse `\u002Focto:issues list` to see all open issues.\n```\n\n\n## File Management\n\n### Initialize ISSUES.md\n\n**When:** First time skill is used or `.octo\u002FISSUES.md` doesn't exist.\n\n**Action:**\n\n```bash\n# Create .octo directory if needed\nmkdir -p .octo\n\n# Copy template\ncp ${CLAUDE_PLUGIN_ROOT:-${CODEX_PLUGIN_ROOT:-${HOME}\u002F.claude-octopus\u002Fplugin}}\u002Fconfig\u002Ftemplates\u002FISSUES.md.template .octo\u002FISSUES.md\n\n# Replace {{PROJECT_NAME}} with actual project name\nPROJECT_NAME=$(basename $(pwd))\nsed -i '' \"s\u002F{{PROJECT_NAME}}\u002F$PROJECT_NAME\u002Fg\" .octo\u002FISSUES.md\n```\n\n### Preserve Existing Issues\n\n**CRITICAL:** When adding or resolving issues, NEVER overwrite existing content.\n\n**Pattern:**\n\n```bash\n# Read existing content\nEXISTING=$(cat .octo\u002FISSUES.md)\n\n# Modify specific section only\n# Append new issue to Open Issues table\n# OR move issue from Open to Resolved\n\n# Write back with all content preserved\necho \"$MODIFIED\" > .octo\u002FISSUES.md\n```\n\n\n## ID Generation Algorithm\n\n**Format:** `ISS-YYYYMMDD-NNN`\n\n**Example:** `ISS-20260203-001`\n\n**Implementation:**\n\n```bash\n#!\u002Fbin\u002Fbash\n\n# Get today's date in YYYYMMDD format\nTODAY=$(date +%Y%m%d)\n\n# Find all issues created today\nTODAY_ISSUES=$(grep -o \"ISS-${TODAY}-[0-9]\\{3\\}\" .octo\u002FISSUES.md || echo \"\")\n\nif [ -z \"$TODAY_ISSUES\" ]; then\n  # No issues today, start at 001\n  NEXT_NUM=\"001\"\nelse\n  # Get highest number for today\n  HIGHEST=$(echo \"$TODAY_ISSUES\" | sed \"s\u002FISS-${TODAY}-\u002F\u002F\" | sort -n | tail -1)\n  \n  # Increment\n  NEXT_NUM=$(printf \"%03d\" $((10#$HIGHEST + 1)))\nfi\n\n# Generate ID\nISSUE_ID=\"ISS-${TODAY}-${NEXT_NUM}\"\necho \"$ISSUE_ID\"\n```\n\n\n## Severity Levels\n\n| Level | Meaning | Example |\n|-------|---------|---------|\n| **critical** | Blocks all progress | Production down, data loss |\n| **high** | Significant impact | Feature broken, security issue |\n| **medium** | Should address | Performance degradation, UX issue |\n| **low** | Nice to fix | Minor bug, cosmetic issue |\n\n\n## Integration with Other Skills\n\n### With skill-debug\n\n```\nUser: \"track this bug for later\"\n\n1. Use skill-issues to create issue\n2. Use skill-debug to investigate if time permits\n3. Link issue ID in debug notes\n```\n\n### With skill-task-management\n\n```\nUser: \"add fixing ISS-20260203-001 to todos\"\n\n1. Use skill-task-management to add todo\n2. Reference issue ID in todo description\n3. Mark issue as resolved when todo completes\n```\n\n### With flow-develop\n\n```\nUser: \"implement fix for ISS-20260203-001\"\n\n1. Use flow-develop to implement fix\n2. Use skill-issues to resolve issue after fix\n3. Link commit SHA in resolution notes\n```\n\n\n## Best Practices\n\n### 1. Clear Descriptions\n\n**Good:**\n```\nAuth token refresh fails after 15 minutes\n```\n\n**Poor:**\n```\nAuth broken\n```\n\n### 2. Appropriate Severity\n\n**Critical:** Only for blockers that stop all work\n**High:** Significant but workarounds exist\n**Medium:** Should fix but not urgent\n**Low:** Nice to have\n\n### 3. Resolution Notes\n\n**Good:**\n```\nFixed OAuth token refresh by updating expiration logic in auth.ts\nCommit: abc123\n```\n\n**Poor:**\n```\nFixed\n```\n\n\n## Common Patterns\n\n### Pattern 1: Track During Development\n\n```\nUser: \"track this issue: API rate limiting not working\"\n\nAction:\n1. Create issue with appropriate severity\n2. Record current phase from STATE.md\n3. Continue development\n```\n\n### Pattern 2: Resolve After Fix\n\n```\nUser: \"resolve ISS-20260203-001, fixed in commit abc123\"\n\nAction:\n1. Ask for resolution notes\n2. Move to Resolved section\n3. Record resolution date and notes\n```\n\n### Pattern 3: Review Open Issues\n\n```\nUser: \"what issues do we have?\"\n\nAction:\n1. List all open issues\n2. Show severity and phase\n3. Offer to show details or resolve\n```\n\n\n## Red Flags - Don't Do This\n\n| Action | Why It's Wrong |\n|--------|----------------|\n| Overwrite ISSUES.md | Lose all existing issues |\n| Skip severity validation | Invalid data in file |\n| Duplicate issue IDs | ID collision |\n| Vague descriptions | Can't remember what issue was |\n| Resolve without notes | No record of what was done |\n\n\n## Quick Reference\n\n| User Intent | Skill Action | Output |\n|-------------|--------------|--------|\n| \"list issues\" | Read and display Open Issues | Table of issues |\n| \"add issue X\" | Generate ID, append to file | Issue created |\n| \"resolve ISS-X\" | Move to Resolved section | Issue resolved |\n| \"show ISS-X\" | Find and display details | Issue details |\n\n\n## The Bottom Line\n\n```\nIssue tracking → Persistent memory across sessions\nOtherwise → Forget problems, repeat mistakes\n```\n\n**Track everything. Resolve systematically. Learn from history.**\n","> **Host: Codex CLI** — This skill was designed for Claude Code and adapted for Codex.\n> Cross-reference commands use installed skill names in Codex rather than `\u002Focto:*` slash commands.\n> Use the active Codex shell and subagent tools. Do not claim a provider, model, or host subagent is available until the current session exposes it.\n> For host tool equivalents, see `skills\u002Fblocks\u002Fcodex-host-adapter.md`.\n\n\n# Issue Tracking\n\n## Overview\n\nCross-session issue tracking for persistent problem management. Issues are stored in `.octo\u002FISSUES.md` and survive across Claude Code sessions.\n\n**Core principle:** Track → Resolve → Learn.\n\n\n## When to Use\n\n**Use this skill when user wants to:**\n- Track a problem or blocker for later\n- Record issues discovered during development\n- Review open issues across sessions\n- Mark issues as resolved\n- View details of specific issues\n\n**Do NOT use for:**\n- GitHub issue management (use gh CLI)\n- Git-tracked issues (use git commands)\n- Temporary todos (use task plan tool)\n\n\n## Subcommands\n\n### 1. List Issues (Default)\n\n**Trigger:** `\u002Focto:issues` or `\u002Focto:issues list`\n\nShow all open issues in table format:\n\n```markdown\n## Open Issues\n\n| ID | Severity | Category | Description | Created | Phase |\n|----|----------|----------|-------------|---------|-------|\n| ISS-20260203-001 | high | integration | Auth not working | 2026-02-03 | Develop |\n| ISS-20260203-002 | medium | performance | Slow query performance | 2026-02-03 | Deliver |\n```\n\n**Pattern Detection:** After listing, check if 3+ open issues share the same category. If so, alert:\n```text\n⚠ Pattern detected: 3 open issues in category \"integration\" — may indicate a systemic problem.\n```\n\n**Implementation:**\n1. Check if `.octo\u002FISSUES.md` exists\n2. If not, initialize from template\n3. Read and parse Open Issues section\n4. Display in table format\n\n\n### 2. Add Issue\n\n**Trigger:** `\u002Focto:issues add \u003Cdescription>`\n\nAdd new issue with auto-generated ID.\n\n**Flow:**\n\n#### Step 1: Gather Information\n\nUse AskUserQuestion with two questions:\n\n```javascript\nAskUserQuestion({\n  questions: [\n    {\n      question: \"What severity is this issue?\",\n      header: \"Severity\",\n      multiSelect: false,\n      options: [\n        {label: \"critical\", description: \"Blocks all progress\"},\n        {label: \"high\", description: \"Significant impact\"},\n        {label: \"medium\", description: \"Should address\"},\n        {label: \"low\", description: \"Nice to fix\"}\n      ]\n    },\n    {\n      question: \"What category does this issue fall into?\",\n      header: \"Category\",\n      multiSelect: false,\n      options: [\n        {label: \"logic-error\", description: \"Incorrect behavior or wrong output\"},\n        {label: \"integration\", description: \"Cross-component or API compatibility\"},\n        {label: \"quality-gate\", description: \"Quality gate failures during workflows\"},\n        {label: \"security\", description: \"Security vulnerabilities or concerns\"},\n        {label: \"performance\", description: \"Speed, memory, or scalability issues\"},\n        {label: \"ux\", description: \"User experience or usability problems\"},\n        {label: \"architecture\", description: \"Structural or design pattern issues\"}\n      ]\n    }\n  ]\n})\n```\n\n#### Step 2: Determine Current Phase\n\n```bash\n# Check if STATE.md exists\nif [ -f .octo\u002FSTATE.md ]; then\n  grep \"current_phase:\" .octo\u002FSTATE.md\nelse\n  echo \"Unknown\"\nfi\n```\n\n#### Step 3: Generate Issue ID\n\n**Format:** `ISS-YYYYMMDD-NNN`\n\n```bash\n# Get today's date\nTODAY=$(date +%Y%m%d)\n\n# Find existing issues for today\ngrep \"ISS-${TODAY}-\" .octo\u002FISSUES.md | tail -1\n\n# Increment sequence number\n# If ISS-20260203-001 exists, next is ISS-20260203-002\n```\n\n#### Step 4: Append to ISSUES.md\n\nAdd new row to Open Issues table:\n\n```markdown\n| ISS-20260203-003 | medium | performance | Slow query performance | 2026-02-03 | Develop |\n```\n\n**Preserve existing issues** - append only, don't overwrite.\n\n#### Step 5: Confirm\n\n```markdown\n✅ Issue created: ISS-20260203-003\n\n**Severity:** medium\n**Category:** performance\n**Description:** Slow query performance\n**Created:** 2026-02-03\n**Phase:** Develop\n\nView with: \u002Focto:issues show ISS-20260203-003\n```\n\n\n### 3. Resolve Issue\n\n**Trigger:** `\u002Focto:issues resolve \u003Cid>`\n\nMark issue as resolved and move to Resolved section.\n\n**Flow:**\n\n#### Step 1: Validate Issue Exists\n\n```bash\n# Check if issue ID exists in Open Issues\ngrep \"ISS-20260203-001\" .octo\u002FISSUES.md\n```\n\nIf not found, show error:\n\n```markdown\n❌ Issue ISS-20260203-001 not found in open issues.\n\nUse `\u002Focto:issues list` to see all open issues.\n```\n\n#### Step 2: Ask for Resolution Notes\n\n```markdown\n**Resolving issue:** ISS-20260203-001\n\nPlease provide resolution notes:\n```\n\n#### Step 3: Move to Resolved Section\n\n1. Extract issue row from Open Issues table\n2. Remove from Open Issues\n3. Add to Resolved Issues with resolution date and notes\n\n**Resolved Issues format:**\n\n```markdown\n| ID | Severity | Category | Description | Created | Resolved | Resolution |\n|----|----------|----------|-------------|---------|----------|------------|\n| ISS-20260203-001 | high | integration | Auth not working | 2026-02-03 | 2026-02-04 | Fixed OAuth token refresh |\n```\n\n#### Step 4: Confirm\n\n```markdown\n✅ Issue resolved: ISS-20260203-001\n\n**Resolution date:** 2026-02-04\n**Resolution notes:** Fixed OAuth token refresh\n\nView with: \u002Focto:issues show ISS-20260203-001\n```\n\n\n### 4. Show Issue Details\n\n**Trigger:** `\u002Focto:issues show \u003Cid>`\n\nDisplay full details of specific issue.\n\n**Flow:**\n\n#### Step 1: Find Issue\n\nSearch both Open and Resolved sections for issue ID.\n\n#### Step 2: Display Details\n\n**For open issue:**\n\n```markdown\n## Issue Details: ISS-20260203-001\n\n**Status:** Open\n**Severity:** high\n**Category:** integration\n**Description:** Auth not working\n**Created:** 2026-02-03\n**Phase:** Develop\n\n**Actions:**\n- Resolve: `\u002Focto:issues resolve ISS-20260203-001`\n```\n\n**For resolved issue:**\n\n```markdown\n## Issue Details: ISS-20260203-001\n\n**Status:** Resolved\n**Severity:** high\n**Category:** integration\n**Description:** Auth not working\n**Created:** 2026-02-03\n**Resolved:** 2026-02-04\n**Resolution:** Fixed OAuth token refresh\n```\n\n#### Step 3: If Not Found\n\n```markdown\n❌ Issue ISS-20260203-001 not found.\n\nUse `\u002Focto:issues list` to see all open issues.\n```\n\n\n## File Management\n\n### Initialize ISSUES.md\n\n**When:** First time skill is used or `.octo\u002FISSUES.md` doesn't exist.\n\n**Action:**\n\n```bash\n# Create .octo directory if needed\nmkdir -p .octo\n\n# Copy template\ncp ${CLAUDE_PLUGIN_ROOT:-${CODEX_PLUGIN_ROOT:-${HOME}\u002F.claude-octopus\u002Fplugin}}\u002Fconfig\u002Ftemplates\u002FISSUES.md.template .octo\u002FISSUES.md\n\n# Replace {{PROJECT_NAME}} with actual project name\nPROJECT_NAME=$(basename $(pwd))\nsed -i '' \"s\u002F{{PROJECT_NAME}}\u002F$PROJECT_NAME\u002Fg\" .octo\u002FISSUES.md\n```\n\n### Preserve Existing Issues\n\n**CRITICAL:** When adding or resolving issues, NEVER overwrite existing content.\n\n**Pattern:**\n\n```bash\n# Read existing content\nEXISTING=$(cat .octo\u002FISSUES.md)\n\n# Modify specific section only\n# Append new issue to Open Issues table\n# OR move issue from Open to Resolved\n\n# Write back with all content preserved\necho \"$MODIFIED\" > .octo\u002FISSUES.md\n```\n\n\n## ID Generation Algorithm\n\n**Format:** `ISS-YYYYMMDD-NNN`\n\n**Example:** `ISS-20260203-001`\n\n**Implementation:**\n\n```bash\n#!\u002Fbin\u002Fbash\n\n# Get today's date in YYYYMMDD format\nTODAY=$(date +%Y%m%d)\n\n# Find all issues created today\nTODAY_ISSUES=$(grep -o \"ISS-${TODAY}-[0-9]\\{3\\}\" .octo\u002FISSUES.md || echo \"\")\n\nif [ -z \"$TODAY_ISSUES\" ]; then\n  # No issues today, start at 001\n  NEXT_NUM=\"001\"\nelse\n  # Get highest number for today\n  HIGHEST=$(echo \"$TODAY_ISSUES\" | sed \"s\u002FISS-${TODAY}-\u002F\u002F\" | sort -n | tail -1)\n  \n  # Increment\n  NEXT_NUM=$(printf \"%03d\" $((10#$HIGHEST + 1)))\nfi\n\n# Generate ID\nISSUE_ID=\"ISS-${TODAY}-${NEXT_NUM}\"\necho \"$ISSUE_ID\"\n```\n\n\n## Severity Levels\n\n| Level | Meaning | Example |\n|-------|---------|---------|\n| **critical** | Blocks all progress | Production down, data loss |\n| **high** | Significant impact | Feature broken, security issue |\n| **medium** | Should address | Performance degradation, UX issue |\n| **low** | Nice to fix | Minor bug, cosmetic issue |\n\n\n## Integration with Other Skills\n\n### With skill-debug\n\n```\nUser: \"track this bug for later\"\n\n1. Use skill-issues to create issue\n2. Use skill-debug to investigate if time permits\n3. Link issue ID in debug notes\n```\n\n### With skill-task-management\n\n```\nUser: \"add fixing ISS-20260203-001 to todos\"\n\n1. Use skill-task-management to add todo\n2. Reference issue ID in todo description\n3. Mark issue as resolved when todo completes\n```\n\n### With flow-develop\n\n```\nUser: \"implement fix for ISS-20260203-001\"\n\n1. Use flow-develop to implement fix\n2. Use skill-issues to resolve issue after fix\n3. Link commit SHA in resolution notes\n```\n\n\n## Best Practices\n\n### 1. Clear Descriptions\n\n**Good:**\n```\nAuth token refresh fails after 15 minutes\n```\n\n**Poor:**\n```\nAuth broken\n```\n\n### 2. Appropriate Severity\n\n**Critical:** Only for blockers that stop all work\n**High:** Significant but workarounds exist\n**Medium:** Should fix but not urgent\n**Low:** Nice to have\n\n### 3. Resolution Notes\n\n**Good:**\n```\nFixed OAuth token refresh by updating expiration logic in auth.ts\nCommit: abc123\n```\n\n**Poor:**\n```\nFixed\n```\n\n\n## Common Patterns\n\n### Pattern 1: Track During Development\n\n```\nUser: \"track this issue: API rate limiting not working\"\n\nAction:\n1. Create issue with appropriate severity\n2. Record current phase from STATE.md\n3. Continue development\n```\n\n### Pattern 2: Resolve After Fix\n\n```\nUser: \"resolve ISS-20260203-001, fixed in commit abc123\"\n\nAction:\n1. Ask for resolution notes\n2. Move to Resolved section\n3. Record resolution date and notes\n```\n\n### Pattern 3: Review Open Issues\n\n```\nUser: \"what issues do we have?\"\n\nAction:\n1. List all open issues\n2. Show severity and phase\n3. Offer to show details or resolve\n```\n\n\n## Red Flags - Don't Do This\n\n| Action | Why It's Wrong |\n|--------|----------------|\n| Overwrite ISSUES.md | Lose all existing issues |\n| Skip severity validation | Invalid data in file |\n| Duplicate issue IDs | ID collision |\n| Vague descriptions | Can't remember what issue was |\n| Resolve without notes | No record of what was done |\n\n\n## Quick Reference\n\n| User Intent | Skill Action | Output |\n|-------------|--------------|--------|\n| \"list issues\" | Read and display Open Issues | Table of issues |\n| \"add issue X\" | Generate ID, append to file | Issue created |\n| \"resolve ISS-X\" | Move to Resolved section | Issue resolved |\n| \"show ISS-X\" | Find and display details | Issue details |\n\n\n## The Bottom Line\n\n```\nIssue tracking → Persistent memory across sessions\nOtherwise → Forget problems, repeat mistakes\n```\n\n**Track everything. Resolve systematically. Learn from history.**\n",{"name":5,"description":7,"disable-model-invocation":42},true,"main","f620abaff09061f8c8b1f1559dca3fdd031a32e5","plugins\u002Fnyldn\u002Fclaude-octopus\u002Fskills\u002Fskill-issues",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":42},[55,58,61],{"tool":56,"command":57},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill skill-issues",{"tool":59,"command":60},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill skill-issues",{"tool":62,"command":63},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill skill-issues","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fnyldn\u002Fclaude-octopus\u002Fskills\u002Fskill-issues\u002FSKILL.md",[66],{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"agents\u002Fopenai.yaml","REFERENCE","参考文档",164,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fnyldn\u002Fclaude-octopus\u002Fskills\u002Fskill-issues\u002Fagents\u002Fopenai.yaml",[73,83,91,99,107,115],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":77,"licenseFileUrl":78,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":82},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":77,"licenseFileUrl":87,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":82},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":77,"licenseFileUrl":95,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":82},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":77,"licenseFileUrl":103,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":82},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":77,"licenseFileUrl":111,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":82},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":77,"licenseFileUrl":119,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":82},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]