Install
$ agentstack add skill-davila7-claude-with-skills-fix-issue ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
Fix GitHub issue
Step 1: Read the issue
Run:
gh issue view $ARGUMENTS
If the issue does not exist or the gh CLI is not authenticated, stop and report the error. Do not proceed.
Step 2: Understand the requirements
From the issue output, identify:
- The reported problem or requested feature
- Any reproduction steps or acceptance criteria mentioned in the issue body
- Labels that indicate the type of work (bug, enhancement, documentation, etc.)
- Any linked issues or pull requests that provide additional context
If the issue is unclear or underspecified, state the assumptions you are making before proceeding.
Step 3: Find the relevant code
Search for code related to the issue:
- Use
grep -rto find files referencing the relevant function, component, or error message - Read the most relevant files to understand the current implementation
- Identify where the change should be made and why
Step 4: Implement a minimal fix
Make the smallest change that correctly addresses the issue. Follow the existing code patterns in the affected file:
- Match the style, naming conventions, and error handling patterns already in use
- Do not refactor unrelated code
- Do not add features beyond what the issue describes
Step 5: Write or update tests
If the codebase has tests:
- Add a test that fails before the fix and passes after
- Update any existing tests that are affected by the change
- Run the existing tests to confirm nothing is broken (use the test runner you find in
package.jsonor the nearest test configuration file)
If you cannot determine the test runner, note that and ask the user.
Step 6: Prepare a commit message
Stage the changes and write a commit message in this format:
fix:
Fixes #$ARGUMENTS
Do not commit automatically. Present the staged diff and the proposed commit message, then wait for the user to confirm or adjust before committing.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: davila7
- Source: davila7/claude-with-skills
- License: MIT
- Homepage: https://claude-with-skills.vercel.app
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.