feat(secdevai-tool): refined SKILL.md#17
Conversation
- Introduce `tool_resolution` mapping to select security tools per programming language (Python, Go, Java, JavaScript, Rust)
- Add structured `input_schema` defining allowed tool selection (`bandit`, `gosec`, `scorecard`, `semgrep`, `all`)
- Standardize script path usage via `${BASE_DIR}` for container execution helper script
- Refactor tool execution documentation with clearer per-tool sections (Bandit, GoSec, Scorecard, Semgrep)
- Improve Semgrep container workflow
- Add `language_detection` rules based on common project files for automatic tool configuration
- Provide explicit example of Semgrep command construction with multiple `--config` flags
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Enterprise Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Tip 💬 Introducing Slack Agent: The best way for teams to turn conversations into code.Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.
Built for teams:
One agent for your entire SDLC. Right inside Slack. 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 |
tool_resolutionmapping to select security tools per programming language (Python, Go, Java, JavaScript, Rust)input_schemadefining allowed tool selection (bandit,gosec,scorecard,semgrep,all)${BASE_DIR}for container execution helper scriptlanguage_detectionrules based on common project files for automatic tool configuration--configflags