[FEAT]: Setup agents.md file with relevant skills for the repo#446
[FEAT]: Setup agents.md file with relevant skills for the repo#446AshutoshDash1999 wants to merge 2 commits into
Conversation
📝 WalkthroughWalkthroughAdds five new agent skill documents ( ChangesAgent Skill Documents
Repo Agent Wiring and Landing Tooling
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Suggested labels
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment Warning |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (2)
.agents/skills/wcag-audit-patterns/SKILL.md (2)
40-58: ⚡ Quick winAdd language specification to fenced code block.
Line 40 has a fenced code block without a language specification. Specify
textto enable proper syntax highlighting.📝 Proposed fix
-``` +```text Critical (Blockers): ├── Missing alt text for functional images ├── No keyboard access to interactive elements ├── Missing form labels └── Auto-playing media without controls Serious: ├── Insufficient color contrast ├── Missing skip links ├── Inaccessible custom widgets └── Missing page titles Moderate: ├── Missing language attribute ├── Unclear link text ├── Missing landmarks └── Improper heading hierarchy -``` +```🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In @.agents/skills/wcag-audit-patterns/SKILL.md around lines 40 - 58, The fenced code block containing the WCAG audit patterns list (starting with "Critical (Blockers):") is missing a language specification. Add `text` as the language identifier immediately after the opening triple backticks (```) on line 40 to enable proper syntax highlighting for the block containing the accessibility audit severity levels and their corresponding issues.
31-36: ⚡ Quick winAdd language specification to fenced code block.
Line 31 has a fenced code block without a language specification. Specify
textto enable proper syntax highlighting.📝 Proposed fix
-``` +```text Perceivable: Can users perceive the content? Operable: Can users operate the interface? Understandable: Can users understand the content? Robust: Does it work with assistive tech? -``` +```🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In @.agents/skills/wcag-audit-patterns/SKILL.md around lines 31 - 36, The fenced code block containing the WCAG principles (Perceivable, Operable, Understandable, Robust) is missing a language specification. Add `text` immediately after the opening triple backticks on the line before "Perceivable:" to enable proper syntax highlighting in the markdown file.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.agents/skills/docker-expert/SKILL.md:
- Line 14: The "When invoked:" heading uses h3 markdown syntax (###) but should
use h2 syntax (##) to maintain proper heading hierarchy after the h1 title at
the top of the document. Change the heading marker from ### to ## for "When
invoked:" to ensure correct semantic structure and document navigation flow.
---
Nitpick comments:
In @.agents/skills/wcag-audit-patterns/SKILL.md:
- Around line 40-58: The fenced code block containing the WCAG audit patterns
list (starting with "Critical (Blockers):") is missing a language specification.
Add `text` as the language identifier immediately after the opening triple
backticks (```) on line 40 to enable proper syntax highlighting for the block
containing the accessibility audit severity levels and their corresponding
issues.
- Around line 31-36: The fenced code block containing the WCAG principles
(Perceivable, Operable, Understandable, Robust) is missing a language
specification. Add `text` immediately after the opening triple backticks on the
line before "Perceivable:" to enable proper syntax highlighting in the markdown
file.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: 4bd8d46c-3ca3-402c-8efd-cffd7518643a
📒 Files selected for processing (16)
.agents/skills/docker-expert/SKILL.md.agents/skills/python-design-patterns/SKILL.md.agents/skills/python-design-patterns/references/details.md.agents/skills/python-observability/SKILL.md.agents/skills/python-observability/references/details.md.agents/skills/seo-audit/SKILL.md.agents/skills/seo-audit/evals/evals.json.agents/skills/seo-audit/references/ai-writing-detection.md.agents/skills/seo-audit/references/international-seo.md.agents/skills/wcag-audit-patterns/SKILL.md.agents/skills/wcag-audit-patterns/references/details.mdAGENTS.mdagentwatch-landing/.gitignoreagentwatch-landing/AGENTS.mdagentwatch-landing/package.jsonskills-lock.json
|
|
||
| You are an advanced Docker containerization expert with comprehensive, practical knowledge of container optimization, security hardening, multi-stage builds, orchestration patterns, and production deployment strategies based on current industry best practices. | ||
|
|
||
| ### When invoked: |
There was a problem hiding this comment.
Heading level skip from h1 to h3 (missing h2).
The "When invoked:" heading uses h3 (###) but should use h2 (##) to maintain proper hierarchy after the h1 title. This improves semantic structure and navigation.
🔧 Proposed fix
-### When invoked:
+## When invoked:📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| ### When invoked: | |
| ## When invoked: |
🧰 Tools
🪛 markdownlint-cli2 (0.22.1)
[warning] 14-14: Heading levels should only increment by one level at a time
Expected: h2; Actual: h3
(MD001, heading-increment)
🪛 SkillSpector (2.1.1)
[info] 63: [TM1] Tool Parameter Abuse: Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
Remediation: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
(Tool Misuse (TM1))
[warning] 247: [TM3] Unsafe Defaults: Tool defaults are unsafe or overly permissive (e.g. disabled TLS verification, no authentication, world-writable permissions). Unsafe defaults widen the attack surface.
Remediation: Override unsafe defaults with secure settings (verify=True, auth required, restrictive permissions). Review and harden all tool configurations.
(Tool Misuse (TM3))
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In @.agents/skills/docker-expert/SKILL.md at line 14, The "When invoked:"
heading uses h3 markdown syntax (###) but should use h2 syntax (##) to maintain
proper heading hierarchy after the h1 title at the top of the document. Change
the heading marker from ### to ## for "When invoked:" to ensure correct semantic
structure and document navigation flow.
Source: Linters/SAST tools
🧪 PR Test Results
Python 3.12 · commit 9f3b1bf |
sreerevanth
left a comment
sreerevanth
left a comment
There was a problem hiding this comment.
Thanks for the contribution. We do use AGENTS.md workflows with agentic coding tools. Before merging, can you explain the rationale for including seo-audit and wcag-audit-patterns alongside the Python/DevOps skills? I'd like to understand how they fit AgentWatch's contributor workflow and whether we should keep only core repository skills.
2 participants
Description
Closes #231
docker-expertpython-design-patternspython-observabilityseo-auditwcag-audit-patternsLet me know if you need me to add more skills from: https://skills.sh/
Summary by CodeRabbit
Release Notes
New Features
Documentation