Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

create blink manuals

Open
#22 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript
Domain
cli, documentation

Research direction

Start by locating the CLI entry point for blink manual and the current Agents.md injection. Define the Slack and GitHub manual sources and placeholder behavior, then verify the listed commands, invalid-name fallback, edit-mode output, documentation updates, examples, and versioning; confirm the generated context is no longer oversized.

Written by the indexing model from the issue text.

Description

TUI
  • Blink manual command in CLI (blink manual )
    • Description: Implement CLI to list manuals and print Markdown for Slack, GitHub; fallback to list on invalid name
    • Acceptance:
      • blink manual shows available manuals
      • blink manual slack prints Slack manual (Markdown)
      • blink manual github prints GitHub manual (Markdown)
      • Output consumable by LLMs and humans
  • Replace injected Agents.md with manual placeholders
    • Description: Remove large Agents MD injection; reference blink manual instead
    • Acceptance:
      • Edit mode uses placeholders
      • Docs updated; no oversized prompt/context
  • Author initial manuals
    • Slack manual: auth, events, commands, posting, SDK patterns
    • GitHub manual: auth, webhooks, PR review flow, comments, statuses
    • Acceptance: Examples included; copy reviewed; versioned in repo
Dominant language
TypeScript
Stars
165
Forks
20
Avg merge
24m
Merged PRs (30d)
1

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from coder/blink

All issues in coder/blink

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.