all publishers

ForeverAProgrammer

@foreveraprogrammer source repo

32 published skills

  1. ▌
    Create Issue Github · foreveraprogrammer
    Create a GitHub issue from a description provided by the user.
    0 repo stars
  2. ▌
    Tag Release Ansible · foreveraprogrammer
    Bump the version in an Ansible Galaxy collection or role, tag the release, and push.
    0 repo stars
  3. ▌
    Create Mr Gitlab Git · foreveraprogrammer
    Create a GitLab merge request from the current branch, deriving the title and description from the branch's git history.
    0 repo stars
  4. ▌
    Create Pr Github Git · foreveraprogrammer
    Create a GitHub pull request from the current branch, deriving the title and description from the branch's git history.
    0 repo stars
  5. ▌
    Fix Issue Github Auto · foreveraprogrammer
    Fully automate resolving a GitHub issue: create a linked branch, apply code changes, commit, open a PR, and resolve any conflicts.
    0 repo stars
  6. ▌
    Resolve Open Questions · foreveraprogrammer
    Walk through an HLD or LLD's Open Questions, asking the user for real answers, then update the doc — checking off each resolved question, updating the design section it affects, and adding or amending Requirements where the answer creates a new obligation. Use when a design doc has unresolved Open Questions blocking implementation.
    0 repo stars
  7. ▌
    Create Issue Branch Github · foreveraprogrammer
    Create a branch linked to a GitHub issue and check it out locally.
    0 repo stars
  8. ▌
    Pr · foreveraprogrammer
    Generate a pull request title and description based on the summary or diff below. Use when the user wants to write a PR description.
    0 repo stars
  9. ▌
    Hld · foreveraprogrammer
    Generate a High Level Design (HLD) document from a freeform description and write it to a markdown file in the design/ directory. Use when the user wants to design a feature, system, or component at a high level.
    0 repo stars
  10. ▌
    Lld · foreveraprogrammer
    Generate a Low Level Design (LLD) document from a freeform description and write it to a markdown file in the design/ directory. Use when the user wants to document the low-level implementation details of a component.
    0 repo stars
  11. ▌
    Sync · foreveraprogrammer
    Sync the current branch with the latest changes from the default branch.
    0 repo stars
  12. ▌
    Tldr · foreveraprogrammer
    Summarize the following text for a non-technical manager. Use when the user pastes technical content they want simplified.
    0 repo stars
  13. ▌
    Email · foreveraprogrammer
    Turn the following notes into a professional email. Use when the user has rough notes they want turned into a polished email.
    0 repo stars
  14. ▌
    Spike · foreveraprogrammer
    Validate the single highest-risk low-level technical assumption in a design by writing and running a minimal isolated test script, then resolving the corresponding [PENDING SPIKE VALIDATION] tag in the LLD/HLD. Use before locking in low-level design when a key assumption is unproven.
    0 repo stars
  15. ▌
    Commit · foreveraprogrammer
    Generate a git commit message and apply it immediately.
    0 repo stars
  16. ▌
    Review · foreveraprogrammer
    Review code and provide structured feedback. Use when the user wants to review their changes, a file, or pasted code.
    0 repo stars
  17. ▌
    Standup · foreveraprogrammer
    Generate a standup update based on the notes below. Use when the user has rough notes about what they worked on and needs a formatted standup.
    0 repo stars
  18. ▌
    Decision · foreveraprogrammer
    Format a freeform description into a structured Architecture Decision Record (ADR). Use when the user describes a technical decision they made or are making.
    0 repo stars
  19. ▌
    Add Spike · foreveraprogrammer
    Flag an existing HLD or LLD requirement (or add a new one) as needing spike validation before it can be trusted or implemented — inserts a [PENDING SPIKE VALIDATION] tag into the relevant design section and marks the requirement row Needs Spike, cascading the flag to linked docs. Use when a requirement looks simple but actually rests on an unproven technical assumption.
    0 repo stars
  20. ▌
    Changelog · foreveraprogrammer
    Generate or update a changelog file that accumulates history across all releases.
    0 repo stars
  21. ▌
    Reconcile · foreveraprogrammer
    Reverse-update an HLD or LLD doc to match the real code — reads the git diff and spikes since the doc was last reconciled, updates API/Data Model sections to reality, checks off satisfied Requirements, and writes an ADR when the code intentionally diverged from the design. Use to eliminate architectural drift between docs and code.
    0 repo stars
  22. ▌
    Jira Ticket · foreveraprogrammer
    Turn a description into a well-formed Jira/Linear-style ticket with acceptance criteria. Use when the user has a feature idea or bug to capture as a ticket.
    0 repo stars
  23. ▌
    Standup Git · foreveraprogrammer
    Generate a standup update from yesterday's git commits. No input needed.
    0 repo stars
  24. ▌
    Tag Release · foreveraprogrammer
    Suggest and apply the next semver tag based on commits since the last tag.
    0 repo stars
  25. ▌
    Action Items · foreveraprogrammer
    Extract all action items from the text below. Use when the user pastes meeting notes, a conversation, or any text with tasks embedded in it.
    0 repo stars
  26. ▌
    Create Branch · foreveraprogrammer
    Create and checkout a git branch named to match the current uncommitted changes.
    0 repo stars
  27. ▌
    Implement Lld · foreveraprogrammer
    Read a Low Level Design document and apply the code changes it describes to the codebase.
    0 repo stars
  28. ▌
    Jira Ticket Git · foreveraprogrammer
    Turn the current git changes into a well-formed Jira/Linear-style ticket with acceptance criteria.
    0 repo stars
  29. ▌
    Tag Release NPM · foreveraprogrammer
    Bump the npm package version, tag the release, and push.
    0 repo stars
  30. ▌
    Create Pr Github · foreveraprogrammer
    Create a GitHub pull request from the current branch using a description provided by the user.
    0 repo stars
  31. ▌
    Fix Issue Github · foreveraprogrammer
    Read a GitHub issue and apply code changes to resolve it.
    0 repo stars
  32. ▌
    Resolve Conflicts · foreveraprogrammer
    Rebase the current branch onto the target branch to resolve PR conflicts.
    0 repo stars