h3nr1-d14z

Close Engagement — Development skill for Claude Code

Development community

Close and finalize the engagement for: $ARGUMENTS.

How to install Close Engagement

Installs to ~/.claude/commands/h3nr1-d14z-ai-redteam-toolkit-close-engagement.md

Terminal
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/h3nr1-d14z/ai-redteam-toolkit/HEAD/.claude/commands/close-engagement.md -o ~/.claude/commands/h3nr1-d14z-ai-redteam-toolkit-close-engagement.md

Restart Claude Code, or start a new session, for it to be picked up.

What Close Engagement does

Close and finalize the engagement for: $ARGUMENTS

  1. Verify completeness: Check all findings have writeups, CVSS scores, and remediation advice
  2. Final report: Generate engagements//reports/final-report-.md with executive summary, methodology, findings table, risk matrix, remediation priorities
  3. Cleanup: Remove any temp files, tokens, test accounts created during engagement
  4. Evidence archive: Verify all screenshots, logs, PoC scripts are saved in the engagem

Alternatives in Development

  • Engage.Memory — Cross-engagement pattern memory — recall prior techniques, record confirmed findings, housekeeping 348 ★
  • Close Track 334 ★
  • Overnight PRs — Autonomous overnight loop — verify issues against the codebase, close stale ones, ship PRs through /ship (bug 324 ★

Full documentation available on GitHub

View Source Repository