consider observability-engineer agent
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 267
- Forks
- 23
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 12
Description
observability is something i'm seeing more and more of a need for, and would likely fit as a new agent definition. need to /research this field, specifically to look at domain language, etc
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the /research entry point and inspect the existing agent definitions to understand their structure and naming conventions. Research observability engineering terminology and determine what a complete observability-engineer agent definition should cover; done means the proposed scope and definition are documented clearly enough for implementation.
Written by the indexing model from the issue text.
Assessment
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100