ForeverAProgrammer
- 32 skills
- 0 followers
- 8 hours ago last updated
- ▌ Create Issue Github · foreveraprogrammerCreate a GitHub issue from a description provided by the user.
- ▌ Tag Release Ansible · foreveraprogrammerBump the version in an Ansible Galaxy collection or role, tag the release, and push.
- ▌ Create Mr Gitlab Git · foreveraprogrammerCreate a GitLab merge request from the current branch, deriving the title and description from the branch's git history.
- ▌ Create Pr Github Git · foreveraprogrammerCreate a GitHub pull request from the current branch, deriving the title and description from the branch's git history.
- ▌ Fix Issue Github Auto · foreveraprogrammerFully automate resolving a GitHub issue: create a linked branch, apply code changes, commit, open a PR, and resolve any conflicts.
- ▌ Resolve Open Questions · foreveraprogrammerWalk 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.
- ▌ Create Issue Branch Github · foreveraprogrammerCreate a branch linked to a GitHub issue and check it out locally.
- ▌ Pr · foreveraprogrammerGenerate a pull request title and description based on the summary or diff below. Use when the user wants to write a PR description.
- ▌ Hld · foreveraprogrammerGenerate 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.
- ▌ Lld · foreveraprogrammerGenerate 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.
- ▌
- ▌ Tldr · foreveraprogrammerSummarize the following text for a non-technical manager. Use when the user pastes technical content they want simplified.
- ▌ Email · foreveraprogrammerTurn the following notes into a professional email. Use when the user has rough notes they want turned into a polished email.
- ▌ Spike · foreveraprogrammerValidate 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.
- ▌
- ▌ Review · foreveraprogrammerReview code and provide structured feedback. Use when the user wants to review their changes, a file, or pasted code.
- ▌ Standup · foreveraprogrammerGenerate 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.
- ▌ Decision · foreveraprogrammerFormat a freeform description into a structured Architecture Decision Record (ADR). Use when the user describes a technical decision they made or are making.
- ▌ Add Spike · foreveraprogrammerFlag 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.
- ▌ Changelog · foreveraprogrammerGenerate or update a changelog file that accumulates history across all releases.
- ▌ Reconcile · foreveraprogrammerReverse-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.
- ▌ Jira Ticket · foreveraprogrammerTurn 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.
- ▌ Standup Git · foreveraprogrammerGenerate a standup update from yesterday's git commits. No input needed.
- ▌ Tag Release · foreveraprogrammerSuggest and apply the next semver tag based on commits since the last tag.
- ▌ Action Items · foreveraprogrammerExtract all action items from the text below. Use when the user pastes meeting notes, a conversation, or any text with tasks embedded in it.
- ▌ Create Branch · foreveraprogrammerCreate and checkout a git branch named to match the current uncommitted changes.
- ▌ Implement Lld · foreveraprogrammerRead a Low Level Design document and apply the code changes it describes to the codebase.
- ▌ Jira Ticket Git · foreveraprogrammerTurn the current git changes into a well-formed Jira/Linear-style ticket with acceptance criteria.
- ▌
- ▌ Create Pr Github · foreveraprogrammerCreate a GitHub pull request from the current branch using a description provided by the user.
- ▌
- ▌ Resolve Conflicts · foreveraprogrammerRebase the current branch onto the target branch to resolve PR conflicts.