luigidemasi opened a new issue, #17: URL: https://github.com/apache/camel-kit/issues/17
> Imported from [luigidemasi/camel-kit#23](https://github.com/luigidemasi/camel-kit/issues/23), opened by [luigidemasi](https://github.com/luigidemasi) on 2026-04-30. > Closed by [luigidemasi/camel-kit#25](https://github.com/luigidemasi/camel-kit/pull/25), merged on 2026-05-01. --- ## Description Add a traits system that appends agent-specific capability instructions to skill files during `camel-kit init --ai {agent}`. Inspired by [cc-spex](https://github.com/rhuss/cc-spex)'s composable trait overlays. Each agent has exclusive tools that skills never leverage (e.g., Claude Code's worktrees/cron, Gemini's `read_many_files`, Bob's `switch_mode`, OpenCode's LSP). Traits inject agent-native strategies into skill files at build time, using idempotent HTML comment sentinels (`<!-- TRAIT:agent -->`). ### What was implemented - `applyTraits()` method in `DefaultGenerator` — scans `templates/traits/{agent}/` and appends `.append.md` files to matching skill files - Two granularity levels: SKILL.md-level (strategy) and guide-level (tactics) - Migrated `ClaudeGenerator.appendParallelDispatch()` to a trait file - 24 trait files across 5 agents: - Claude Code: 9 (worktrees, cron, parallel Agent, NotebookEdit, ScheduleWakeup) - Gemini CLI: 5 (read_many_files, TOML auto-approval, named agents) - IBM Bob: 4 (switch_mode, gates, insert_content, browser) - Qwen Code: 2 (serial dispatch, todo_write) - OpenCode: 4 (LSP, step limits, agent types) - 5 new integration tests, all 48 tests passing ### References - ADR-0024: Agent Traits System and `/camel-ship` Autonomous Pipeline - Design spec: `docs/superpowers/specs/2026-04-30-agent-traits-and-ship-design.md` - Tool comparison: `docs/ai-coding-cli-tool-comparison.md` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
