Skip to content
Development
Command

/workflow-issue-formatting

- [ ] Use clear, descriptive headings with proper hierarchy (##, ###) - [ ] Include code examples in triple backticks with language syntax highlighting - [ ] Add screenshots/mockups if UI-related (drag & drop or use image hosting) - [ ] Use task lists (- [ ]) for trackable items

From plugin
whetstone
3038 skills19 agents38 commands
Install
$ npx -y skills add iliaal/whetstone --agent claude-code

How it fires

How this command gets triggered: by you, by Claude, or both.

  • Fires itselfClaude auto-loads it when your prompt matches the work.
  • You can call itInvoke it directly when you want it.
  • Slash command/workflow-issue-formatting

Context preview

What this command does when you run it.

- [ ] Use clear, descriptive headings with proper hierarchy (##, ###) - [ ] Include code examples in triple backticks with language syntax highlighting - [ ] Add screenshots/mockups if UI-related (drag & drop or use image hosting) - [ ] Use task lists (- [ ]) for trackable items

Command definition

workflow-issue-formatting.md

Issue Formatting & Creation

Content Formatting

  • [ ] Use clear, descriptive headings with proper hierarchy (##, ###)
  • [ ] Include code examples in triple backticks with language syntax highlighting
  • [ ] Add screenshots/mockups if UI-related (drag & drop or use image hosting)
  • [ ] Use task lists (- [ ]) for trackable items that can be checked off
  • [ ] Add collapsible sections for lengthy logs or optional details using `<details>` tags

Cross-Referencing

  • [ ] Link to related issues/PRs using #number format
  • [ ] Reference specific commits with SHA hashes when relevant
  • [ ] Link to code using GitHub's permalink feature (press 'y' for permanent link)
  • [ ] Mention relevant team members with @username if needed
  • [ ] Add links to external resources with descriptive text

Code & Examples

# Good example with syntax highlighting and line references


```typescript
// src/services/UserService.ts:42
function processUser(user: User): void {

  // Implementation here

}

Collapsible error logs

<details> <summary>Full error stacktrace</summary>

`Error details here...`

</details>


## AI-Era Considerations

- [ ] Account for accelerated development with AI pair programming
- [ ] Include prompts or instructions that worked well during research
- [ ] Note which AI tools were used for initial exploration (Claude, Copilot, etc.)
- [ ] Emphasize comprehensive testing given rapid implementation
- [ ] Document any AI-generated code that needs human review

## Issue Creation

When user selects "Create Issue", detect their project tracker from CLAUDE.md:

1. **Check for tracker preference** in user's CLAUDE.md (global or project):
   - Look for `project_tracker: github` or `project_tracker: linear`
   - Or look for mentions of "GitHub Issues" or "Linear" in their workflow section

2. **If GitHub:**

   Use the title and type from Step 2 (already in context - no need to re-read the file):

   ```bash
   gh issue create --title "<type>: <title>" --body-file <plan_path>

3. **If Linear:**

   linear issue create --title "<title>" --description "$(cat <plan_path>)"

4. **If no tracker configured:** Ask user: "Which project tracker do you use? (GitHub/Linear/Other)"

  • Suggest adding `project_tracker: github` or `project_tracker: linear` to their CLAUDE.md

5. **After creation:**

  • Display the issue URL
  • Ask if they want to proceed to `/ia-work` or `/ia-review`
Read more
Ships withwhetstone

A Claude Code plugin that makes AI coding agents follow engineering discipline. Plan before coding. Verify before claiming done. Find root cause before patching. Review before merge. Skills activate based on file type and task signals, not manual toggling.

Get the whole plugin, auto-invoked
Stats
30
Stars
0
Views
3
Forks
Active
Maintenance
Python
Language
MIT
License
3d ago
Last commit
5mo ago
Created

Repo: iliaal/whetstone