99problems

name	99problems
description	Retrieve historical issue and pull request context from trackers and code hosts to support current engineering tasks.
license	Apache-2.0
compatibility	Requires the `99problems` CLI in PATH. Install or update with npm (`npm install -g @mbe24/99problems`). Cargo installation is also supported.
metadata	{"author":"Mikael Beyene","version":"1.0"}

99problems Skill

When To Use This Skill

Use this skill when current implementation work needs reliable context from prior issues or pull requests in GitHub, GitLab, Jira, or Bitbucket. Use it to recover decisions, constraints, and related work items before proposing changes.

Required Inputs

• Provider context via --instance or explicit flags (--platform, --repo, --url, --deployment)
• Search query (-q) or single identifier (--id)
• Optional token configured in .99problems or via environment variables

Workflow

1. Resolve the target platform and repository/project.
2. If prior context is likely relevant, start with targeted search (-q) to discover related issues/PRs.
3. Fetch key items by identifier (--id) for precise context capture.
4. Select output shape (--format, --output-mode) and payload controls (--no-comments, --no-links).
5. Run 99problems get ..., extract constraints/decisions, and hand off a concise context summary.

Command Patterns

Issue Search

99problems get --instance github -q "repo:owner/repo is:issue state:open"

Pull Request Search

99problems get --instance github -q "repo:owner/repo is:pr state:open" --type pr

Fetch Issue by ID

99problems get --instance github --repo owner/repo --id 1842 --type issue

Fetch Pull Request by ID

99problems get --instance github --repo owner/repo --id 2402 --type pr --include-review-comments

Fetch Jira Issue by Key

99problems get --instance jira-work --id CAM-19831 --type issue

Fetch Bitbucket Pull Request by ID

99problems get --instance bitbucket-cloud --id 1 --type pr --include-review-comments

Output Handling

• For machine pipelines, prefer --format jsonl and stream mode.
• For human inspection, use default TTY text output or --format yaml.
• Use --no-links and --no-comments when payload size should be minimized.

Boundaries

• Jira supports issues only (no PRs).
• Bitbucket support is PR-only.
• This skill does not parse free-text links; use provider APIs and supported flags.

Troubleshooting

• Authentication errors: configure token in .99problems or env vars.
• Empty output: verify query qualifiers (repo:, is:issue, is:pr, state:).
• Unexpected type errors: set --type explicitly (issue or pr) when the target is ambiguous.

Progressive Disclosure

Keep this file concise. Move detailed recipes to references/REFERENCE.md and reusable forms to references/FORMS.md.

Optional directories for expansion:

• scripts/ for executable helpers
• assets/ for static templates/data