Background
Investigation concluded that daf git add-comment is a thin wrapper with zero session integration. It only:
- Detects platform (GitHub vs GitLab) from git remote
- Calls
client.add_comment(issue_key, comment)
- Which under the hood runs
gh issue comment or glab issue note
The gh-cli and glab-cli skills already teach Claude the raw CLI equivalents.
Files to Remove
devflow/cli/commands/git_add_comment_command.py (93 lines)
tests/test_git_add_comment_command.py
Files to Modify
devflow/cli/main.py — remove add-comment subcommand registration
devflow/cli/commands/git_commands.py — remove import if present
.claude/skills/daf-git/SKILL.md — remove daf git add-comment section, add note to use gh issue comment / glab issue note directly
Skill-Based Replacement
The gh-cli skill already documents:
gh issue comment 123 --body "Work in progress"
The glab-cli skill already documents:
glab issue note 123 -m "Work in progress"
The daf-git skill should be updated to reference these directly.
Risk
Low — no session integration, no downstream dependencies.
Background
Investigation concluded that
daf git add-commentis a thin wrapper with zero session integration. It only:client.add_comment(issue_key, comment)gh issue commentorglab issue noteThe
gh-cliandglab-cliskills already teach Claude the raw CLI equivalents.Files to Remove
devflow/cli/commands/git_add_comment_command.py(93 lines)tests/test_git_add_comment_command.pyFiles to Modify
devflow/cli/main.py— removeadd-commentsubcommand registrationdevflow/cli/commands/git_commands.py— remove import if present.claude/skills/daf-git/SKILL.md— removedaf git add-commentsection, add note to usegh issue comment/glab issue notedirectlySkill-Based Replacement
The
gh-cliskill already documents:gh issue comment 123 --body "Work in progress"The
glab-cliskill already documents:glab issue note 123 -m "Work in progress"The
daf-gitskill should be updated to reference these directly.Risk
Low — no session integration, no downstream dependencies.