AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Implement Issue

skill-jartan-llc-grimoire-implement-issue · by Jartan-LLC

Implement a GitHub issue, optionally from an existing plan

No reviews yet
0 installs
20 views
0.0% view→install

Install

$ agentstack add skill-jartan-llc-grimoire-implement-issue

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-jartan-llc-grimoire-implement-issue)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
16d ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Implement Issue? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Implement Issue

Implement changes for a GitHub issue.

Process

1. Load Context

Determine the issue number from the user's request, which may carry context beyond the number. Fetch the issue and any plan comments:

gh issue view  --comments

Also check .claude/workspace/ for any plan files related to this issue. If no plan exists for a complex issue, suggest running /praxis:plan-issue first.

2. Setup Branch

Check existing local and remote branches for one related to this issue -- it may be named by issue number (feature/issue-123) or by description (feature/audit-improvements). If one exists, check it out. If not, create a new branch. For sub-issues of a larger feature, branch from the parent feature branch rather than main.

3. Read Relevant Docs

Based on the issue area, read the appropriate project documentation in docs/.

4. Implement

Follow the plan if one exists. Work through changes methodically. Make progressive commits as logical units of work are completed rather than one monolithic commit at the end.

5. Update Documentation

Changed behavior may need doc updates. Commit doc changes.

6. Verify

Run the Verify commands from CLAUDE.md. Fix any failures and commit the fixes before pushing.

7. Push

Push the branch with all commits.

8. Post Summary

gh issue comment  --body "## Implementation Complete

Branch: \`\`

### Changes
- [categorized list of what was added/modified/removed]

### Documentation
- [docs created or updated, or 'No doc changes needed']

---
*Generated by Claude -- reply with \`/praxis:create-pr \` to create a pull request*"

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.