Skip to content

Rename example hawk tool references to graycode - #42

Merged
Patel230 merged 1 commit into
mainfrom
fix/remove-hawk-example-names
Sep 7, 2026
Merged

Rename example hawk tool references to graycode#42
Patel230 merged 1 commit into
mainfrom
fix/remove-hawk-example-names

Conversation

@Patel230

@Patel230 Patel230 commented Sep 7, 2026

Copy link
Copy Markdown
Contributor

The hawk agent name is gone (rebranded to graycode in PR #40). Six skills used hawk as a generic example CLI/binary name, which now reads as leftover branding:

  • cmd/hawk -> cmd/graycode (spec-driven-development, planning-and-task-breakdown, incremental-implementation, debugging-and-error-recovery)
  • hawk tools -> graycode tools (context-engineering)
  • hawk db migrate / .hawkrc -> graycode db migrate / .graycoderc (rb-changelog)

Intentionally unchanged (genuine third-party content, not our branding)

  • StackHawk (DAST/ASPM product, stackhawk.com) - real product with config files and docs
  • Nighthawk (Cobalt Strike C2 component) - real product
  • HawkEye (typosquatting detection tool, hawk-eye.io) - real product
  • starling chemprop SMILES method in sci-rowan - real API method name; renaming method="starling" would break the code
  • English words (hawking, Hawkins, Hawke) and podcast transcripts - legitimate content

Renaming any of the above would corrupt factual skill content.

The hawk agent name is gone (rebranded to graycode in PR #40). These six
skills used 'hawk' as a generic example CLI/binary name (cmd/hawk, .hawkrc,
'hawk db migrate', 'hawk tools'), which now reads as leftover branding.
Rename them to 'graycode' to match the current agent name.

Genuine third-party references (StackHawk, Nighthawk, HawkEye, chemprop
'starling' method) are intentionally left unchanged - renaming them would
corrupt factual skill content.
@Patel230
Patel230 merged commit 6f6163a into main Sep 7, 2026
6 checks passed
@Patel230
Patel230 deleted the fix/remove-hawk-example-names branch September 7, 2026 03:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant