Create a repo with both code/docs and metadata, not just the remote shell.
README.md if present.package.json, pyproject.toml, etc.) if present.public or private)gh repo create ... --description ... [--homepage ...]gh repo edit ... --add-topic ...gh repo view --json name,description,homepageUrl,repositoryTopics,url or gh api.Treat GitHub About as the combination of:
Do not stop after setting only description.
Topics are mandatory by default.
Prefer 3-5 concise lowercase topics.
Avoid generic filler topics like code, app, or project unless they are truly useful.
Keep the description to one sentence.
If README is missing, create a minimal one before publishing.
If the user says “fill the about section,” interpret that as description + homepage + topics.
Treat an empty repositoryTopics result during verification as a failed task state, not a soft warning.
Derive topics from:
cli, library, automation, bot, tooling, etc.)Good examples:
cli,github,automationtypescript,react,chrome-extensionpython,fastapi,apiCreate repo:
bash
gh repo create <name> --public --description "<summary>"
Add homepage and topics:
bash
gh repo edit <owner>/<repo> \
--homepage "<url>" \
--add-topic topic1 \
--add-topic topic2 \
--add-topic topic3
Verify:
bash
gh repo view <owner>/<repo> --json name,description,homepageUrl,repositoryTopics,url
Verification passes only if repositoryTopics is non-empty.
references/prompt-templates.md when the user wants a reusable prompt for Codex, Claude, or another agent.scripts/lazygithub.sh when a single command is faster than repeated manual gh commands.