dpnmw/agents
1
0
Fork 0
mirror of https://github.com/wshobson/agents.git synced 2026-03-18 09:37:15 +00:00
Code Issues Packages Projects Releases Wiki Activity

Format all YAML files to pass yamllint validation

Browse Source 
- Added document start markers (---) to all YAML files
- Fixed line length issues by breaking long lines appropriately
- Removed trailing whitespace throughout all files
- Added proper newlines at end of files
- Fixed truthy value format ('on' -> 'on')
- Standardized YAML formatting across workflows and issue templates
- Used multi-line strings (>) for long descriptions
- Maintained readability while adhering to 80-character line limit

All YAML files now pass yamllint validation with only minor warnings remaining.
This commit is contained in:
Seth Hobson
2025-08-01 17:33:42 -04:00
parent fe236a76b5
commit 4dad1937e9
7 changed files with 224 additions and 107 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
.github/ISSUE_TEMPLATE/bug_report.yml vendored
View File

@@ -1,3 +1,4 @@
---
name: Bug Report
description: Report a bug or issue with an existing subagent
title: "[BUG] "
@@ -6,9 +7,12 @@ body:
- type: markdown
attributes:
value: |
Thank you for reporting a bug! Please fill out this template to help us understand and resolve the issue.
**Important**: This template is for technical bugs only. For questions, discussions, or general feedback, please use GitHub Discussions instead.
Thank you for reporting a bug! Please fill out this template
to help us understand and resolve the issue.
**Important**: This template is for technical bugs only.
For questions, discussions, or general feedback, please use
GitHub Discussions instead.
- type: checkboxes
id: preliminary-checks
@@ -18,7 +22,8 @@ body:
options:
- label: I have read the [Code of Conduct](.github/CODE_OF_CONDUCT.md)
required: true
- label: I have searched existing issues to ensure this is not a duplicate
- label: >-
I have searched existing issues to ensure this is not a duplicate
required: true
- label: This report contains only technical information about a bug
@@ -67,4 +72,4 @@ body:
attributes:
label: Additional Context
description: Any other context, screenshots, or examples
placeholder: Add any other context about the problem here...
placeholder: Add any other context about the problem here...

3
.github/ISSUE_TEMPLATE/config.yml vendored
View File

@@ -1,3 +1,4 @@
---
blank_issues_enabled: false
contact_links:
- name: GitHub Discussions
@@ -8,4 +9,4 @@ contact_links:
about: Read our Code of Conduct and community standards
- name: Contributing Guide
url: https://github.com/wshobson/agents/blob/main/.github/CONTRIBUTING.md
about: Learn how to contribute effectively to this project
about: Learn how to contribute effectively to this project

14
.github/ISSUE_TEMPLATE/feature_request.yml vendored
View File

@@ -1,3 +1,4 @@
---
name: Feature Request
description: Suggest an improvement or new feature for existing subagents
title: "[FEATURE] "
@@ -6,9 +7,11 @@ body:
- type: markdown
attributes:
value: |
Thank you for suggesting a feature! Please provide detailed information to help us understand your request.
**Note**: For new subagent proposals, please use the "New Subagent Proposal" template instead.
Thank you for suggesting a feature! Please provide detailed
information to help us understand your request.
**Note**: For new subagent proposals, please use the
"New Subagent Proposal" template instead.
- type: checkboxes
id: preliminary-checks
@@ -18,7 +21,8 @@ body:
options:
- label: I have read the [Code of Conduct](.github/CODE_OF_CONDUCT.md)
required: true
- label: I have searched existing issues to ensure this is not a duplicate
- label: >-
I have searched existing issues to ensure this is not a duplicate
required: true
- label: This is a constructive feature request for legitimate use cases
required: true
@@ -74,4 +78,4 @@ body:
attributes:
label: Additional Context
description: Any other relevant information
placeholder: Add any other context, examples, or screenshots here...
placeholder: Add any other context, examples, or screenshots here...

40
.github/ISSUE_TEMPLATE/moderation_report.yml vendored
View File

@@ -1,16 +1,21 @@
---
name: Moderation Report
description: Report inappropriate content, behavior, or Code of Conduct violations
description: >-
Report inappropriate content, behavior, or Code of Conduct violations
title: "[MODERATION] "
labels: ["moderation"]
body:
- type: markdown
attributes:
value: |
**⚠️ Use this template to report violations of our Code of Conduct, inappropriate content, or concerning behavior.**
All reports are taken seriously and will be reviewed by maintainers. False reports may result in moderation action.
**For urgent safety concerns or severe violations, you may also use GitHub's built-in reporting tools.**
**⚠️ Use this template to report violations of our Code of Conduct,
inappropriate content, or concerning behavior.**
All reports are taken seriously and will be reviewed by maintainers.
False reports may result in moderation action.
**For urgent safety concerns or severe violations, you may also use
GitHub's built-in reporting tools.**
- type: checkboxes
id: preliminary-checks
@@ -22,7 +27,9 @@ body:
required: true
- label: I understand that false reports may result in moderation action
required: true
- label: I have attempted to resolve minor issues through direct communication (if applicable)
- label: >-
I have attempted to resolve minor issues through direct
communication (if applicable)
required: false
- type: dropdown
@@ -46,8 +53,9 @@ body:
id: location
attributes:
label: Location of Violation
description: Where did this occur? (issue number, PR, comment link, etc.)
placeholder: e.g., Issue #123, PR #456, comment in issue #789
description: >-
Where did this occur? (issue number, PR, comment link, etc.)
placeholder: e.g., Issue #123, PR #456, comment in issue #789 # Location
validations:
required: true
@@ -55,14 +63,17 @@ body:
id: user-involved
attributes:
label: User(s) Involved
description: GitHub username(s) of the person(s) involved (if known)
description: >-
GitHub username(s) of the person(s) involved (if known)
placeholder: e.g., @username1, @username2
- type: textarea
id: description
attributes:
label: Description of Violation
description: Detailed description of what happened and why it violates our Code of Conduct
description: >-
Detailed description of what happened and why it violates
our Code of Conduct
placeholder: Please provide specific details about the violation...
validations:
required: true
@@ -84,7 +95,8 @@ body:
attributes:
label: Impact
description: How has this affected you or the community?
placeholder: This behavior has made me feel... It affects the community by...
placeholder: >-
This behavior has made me feel... It affects the community by...
- type: checkboxes
id: previous-reports
@@ -102,5 +114,5 @@ body:
- We may follow up with questions if needed
- We will take appropriate action based on our Code of Conduct
- We will update you on the resolution when possible
Thank you for helping maintain a respectful community.
Thank you for helping maintain a respectful community.

39
.github/ISSUE_TEMPLATE/new_subagent.yml vendored
View File

@@ -1,3 +1,4 @@
---
name: New Subagent Proposal
description: Propose a new specialized subagent for the collection
title: "[NEW AGENT] "
@@ -6,9 +7,12 @@ body:
- type: markdown
attributes:
value: |
Thank you for proposing a new subagent! Quality subagents require careful design and clear specialization.
**Important**: Only propose subagents for legitimate, constructive use cases. Proposals for malicious or harmful capabilities will be rejected and may result in moderation action.
Thank you for proposing a new subagent! Quality subagents
require careful design and clear specialization.
**Important**: Only propose subagents for legitimate,
constructive use cases. Proposals for malicious or harmful
capabilities will be rejected and may result in moderation action.
- type: checkboxes
id: preliminary-checks
@@ -18,7 +22,8 @@ body:
options:
- label: I have read the [Code of Conduct](.github/CODE_OF_CONDUCT.md)
required: true
- label: I have reviewed existing subagents to ensure this is not a duplicate
- label: >-
I have reviewed existing subagents to ensure this is not a duplicate
required: true
- label: This proposal is for legitimate, constructive use cases only
required: true
@@ -38,7 +43,8 @@ body:
id: domain-expertise
attributes:
label: Domain Expertise
description: What specific domain or technology does this agent specialize in?
description: >-
What specific domain or technology does this agent specialize in?
placeholder: This agent specializes in...
validations:
required: true
@@ -47,7 +53,9 @@ body:
id: unique-value
attributes:
label: Unique Value Proposition
description: How is this different from existing subagents? What unique capabilities does it provide?
description: >-
How is this different from existing subagents?
What unique capabilities does it provide?
placeholder: Unlike existing agents, this one would...
validations:
required: true
@@ -82,12 +90,14 @@ body:
id: examples
attributes:
label: Example Interactions
description: Provide 2-3 example interactions showing how users would work with this agent
description: >-
Provide 2-3 example interactions showing how users would
work with this agent
placeholder: |
**Example 1:**
User: "Implement a smart contract for..."
Agent response: "I'll create a secure smart contract with..."
**Example 2:**
User: "Optimize this blockchain query..."
Agent response: "Let me analyze the query and suggest optimizations..."
@@ -98,8 +108,11 @@ body:
id: expertise-evidence
attributes:
label: Your Expertise
description: What experience or credentials do you have in this domain?
placeholder: I have X years of experience in... I've worked with... I hold certifications in...
description: >-
What experience or credentials do you have in this domain?
placeholder: >-
I have X years of experience in... I've worked with...
I hold certifications in...
validations:
required: true
@@ -107,5 +120,7 @@ body:
id: additional-context
attributes:
label: Additional Context
description: Any other relevant information, resources, or considerations
placeholder: Relevant documentation, similar tools, potential challenges...
description: >-
Any other relevant information, resources, or considerations
placeholder: >-
Relevant documentation, similar tools, potential challenges...