一键导入
debug
Investigate bugs/issues to find concrete, evidence-backed reproduction steps without fixing them. Use when the user reports a bug, failure, regression, flaky behavior, stack trace, unexpected output, or asks to debug/reproduce an issue.
菜单
Investigate bugs/issues to find concrete, evidence-backed reproduction steps without fixing them. Use when the user reports a bug, failure, regression, flaky behavior, stack trace, unexpected output, or asks to debug/reproduce an issue.
Perform grounded, broad code reviews that avoid tunnel vision and low-value findings. Use when asked to review code, changes, diffs, staged/unstaged work, branches, pull requests, or architecture impact of a change.
Ground agent hypotheses in verifiable evidence from source code, docs, issues, and concrete citations before acting. Use when investigating bugs, library behavior, architecture questions, ambiguous errors, or any task where guessing, assumptions, or stale knowledge could lead to wrong changes.
Make Jira Cloud REST API requests via a local helper script using credentials from environment variables or macOS Keychain. Use by default for Jira work: reading, searching, updating tickets, JQL, comments, transitions, ADF payloads, or any request involving Jira issues.
Create or Update Pull Request on Github
Save important information from the current agent conversation into a human-readable Markdown document. Use when the user invokes /save-to-md, asks to save an investigation/decision/summary to an .md file, or wants conversation context captured as documentation or an ADR-like record.
Use jj (Jujutsu) for local version control instead of git. Activate when: the repo has a .jj/ directory, the user or project config mentions jj, the user says 'use jj', or any version control operation is needed in a jj-managed repo. Also use this skill when the user asks to commit, branch, stash, rebase, or perform any git-like operation in a repo that uses jj. If unsure whether the repo uses jj, check for a .jj/ directory.
| name | debug |
| description | Investigate bugs/issues to find concrete, evidence-backed reproduction steps without fixing them. Use when the user reports a bug, failure, regression, flaky behavior, stack trace, unexpected output, or asks to debug/reproduce an issue. |
Help the user reproduce and understand an issue. Do not fix, patch, refactor, or propose fixes unless the user explicitly asks.
Capture the report
Inspect evidence
Find the suspected source
Reproduce
Instrument when needed
[DEBUGGER] prefix so the user can filter them.[DEBUGGER] lines plus the error/output.Use this structure unless the user requests otherwise:
## Findings
- [Evidence-backed facts]
## Suspected source
- [File/function/code path and why it is implicated]
## Reproduction steps
1. [Exact step]
2. [Exact step]
## Expected vs actual
- Expected: ...
- Actual: ...
## Evidence
- `path:line` / command output / doc or issue URL
## If reproduction is still unclear
Add these temporary logs:
```[language]
console.log("[DEBUGGER] ...", ...)
```
Then run:
```sh
...
```
Paste back the `[DEBUGGER]` lines and the final error/output.
Good [DEBUGGER] logs answer:
Avoid logging secrets, tokens, full PII, or huge payloads. Redact sensitive values.