landing
SkillFiles & storageEnd-of-session ritual. Close finished beads, file new ones for remaining work, run verify, commit in logical groupings, push. Work is not complete until git push succeeds.
Instructions available. Your AI can read the instructions. Execution depends on the setup they require.
Account requirements not reviewed. Check the skill instructions before use; ahel provides instructions and does not run this skill.
Add ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.
Then ask your AI: use the landing skill
What this skill tells your AI
The instructions your AI receives, as published by hoangsonww/forge-agentic-coding-cli in .codex/skills/landing/SKILL.md and read by ahel’s review.
Use the verbatim prompt at .flywheel/prompts/landing.md.
Checklist:
- New beads filed in
.beads/beads.jsonlfor every thread of follow-up work. -
verifyskill passes (format, lint, typecheck, build, tests). - Closed beads updated with a one-line
closed_reason. - Commits are logically grouped with detailed messages, each
referencing bead ids (
fg-12: ...). - No ephemeral files committed.
-
git pull --rebase && git push;git statusclean. - One-line session report: beads closed, beads opened, test count delta, next-session kick-off hint.
Success = a future swarm can pick up the project using only
.beads/beads.jsonl, AGENTS.md, and FLYWHEEL.md.
Signals
- GitHub stars
- 24
- Forks
- 9
- Last commit
- Sep 2026
Others that do the same job
Advanced
- Item type
- skill
- Key
landing-hoangsonww- Source
- github.com/hoangsonww/forge-agentic-coding-cli
github.com/hoangsonww/forge-agentic-coding-cli