Capture
Turn a quick natural-language bug or feature note into a labeled GitHub Issue draft without leaving the agent chat.
Overview
Capture is an agent skill most often used in Build (also Ship, Operate) that turns natural-language feedback into triage-labeled GitHub Issues with CLI and scratchpad fallbacks.
Install
npx skills add https://github.com/camacho/ai-skills --skill captureWhat is this skill?
- Keyword table maps free text to bug vs enhancement plus triage labels
- Creates issues via gh issue create with title, body, and dual labels
- Fallback chain: GitHub MCP, then ai-workspace/scratchpad.md with dated capture
- Hard stop when no description—asks user before proceeding
- Returns issue number and URL on success
- 3-row keyword table for bug vs feature classification
- 2-label issue pattern: triage plus bug or enhancement
Adoption & trust: 638 installs on skills.sh; 1 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You remember a bug or feature in chat but never open GitHub, so the backlog stays empty and context disappears.
Who is it for?
Solo builders on GitHub who want fast issue intake from agent sessions with gh or MCP configured.
Skip if: Teams on Jira/Linear-only workflows, repos without GitHub Issues, or users who need full templates and acceptance criteria in the first pass.
When should I use this skill?
User describes an idea, bug, or feature request in natural language and wants it recorded as a GitHub Issue.
What do I get? / Deliverables
You get a triage GitHub Issue (or a dated scratchpad entry) with type labels and a shareable URL ready for prioritization.
- GitHub Issue with triage and type labels
- Issue URL and number
- Optional scratchpad.md capture entry
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Issue capture is the canonical shelf in Build because solo builders file work while implementing; the same habit applies when triaging after ship or during operate iteration. PM subphase covers backlog intake—this skill is explicitly triage-labeled GitHub Issue creation, not code change.
Where it fits
File a enhancement issue while scoping the next sprint story from a hallway-chat feature idea.
Capture a crash keyword description as bug+triage without switching to the browser.
Log a launch-day regression reported in prose as a labeled issue for hotfix triage.
Append locally to scratchpad when VPN blocks gh, then sync issues when back online.
How it compares
Use instead of manually copying chat text into the GitHub Issues form or ad-hoc TODO comments in code.
Common Questions / FAQ
Who is capture for?
Indie and solo developers who track work in GitHub Issues and want their coding agent to file bugs and enhancements in one step.
When should I use capture?
During build when you spot a defect, during ship when regression language appears, or during operate when you capture iteration ideas—any time you have a free-text description and want a triage issue.
Is capture safe to install?
It runs gh issue create and may write to ai-workspace/scratchpad.md on failure; review the Security Audits panel on this page and scope GitHub tokens to issue creation only.
SKILL.md
READMESKILL.md - Capture
## Inputs - Free-text description of an idea, bug, or feature request ## Steps 1. **Parse the description** to detect type: | Keywords | Type | Labels | |----------|------|--------| | error, crash, broken, fix, bug, fails, regression | Bug | `triage`, `bug` | | add, want, should, new, feature, enhance, improve | Feature | `triage`, `enhancement` | | Default | Feature | `triage`, `enhancement` | 2. **Create GitHub Issue**: ```bash gh issue create \ --title "<concise title from description>" \ --body "<full description>" \ --label "triage" --label "<bug or enhancement>" ``` 3. **Return** the issue number and URL. ## Fallback If `gh` is not available or GitHub access fails: 1. Try GitHub MCP tools (if available) 2. If neither works → append to `ai-workspace/scratchpad.md`: ```markdown ## Captured [date] **Type**: [bug/feature] **Description**: [text] _Failed to create GitHub Issue — saved here as fallback._ ``` Inform the user that the capture was saved locally. ## Edge Cases - No description provided → ask the user to describe the idea/bug - Offline / no GitHub access → scratchpad fallback (see above)