ForeverAProgrammer
UserClaude Code plugin with skills for daily dev workflows — commits, standups, PRs, design docs, and GitHub automation.
Categories
Indexed Skills (31)
hld
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.
implement-lld
Read a Low Level Design document and apply the code changes it describes to the codebase.
lld
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.
add-spike
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.
reconcile
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.
resolve-open-questions
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.
spike
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.
create-mr-gitlab-git
Create a GitLab merge request from the current branch, deriving the title and description from the branch's git history.
tag-release-ansible
Bump the version in an Ansible Galaxy collection or role, tag the release, and push.
changelog
Generate or update a changelog file that accumulates history across all releases.
commit
Generate a git commit message and apply it immediately.
create-branch
Create and checkout a git branch named to match the current uncommitted changes.
create-issue-branch-github
Create a branch linked to a GitHub issue and check it out locally.
create-issue-github
Create a GitHub issue from a description provided by the user.
create-pr-github-git
Create a GitHub pull request from the current branch, deriving the title and description from the branch's git history.
create-pr-github
Create a GitHub pull request from the current branch using a description provided by the user.
decision
Format a freeform description into a structured Architecture Decision Record (ADR). Use when the user describes a technical decision they made or are making.
fix-issue-github
Read a GitHub issue and apply code changes to resolve it.
jira-ticket
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.
pr
Generate a pull request title and description based on the summary or diff below. Use when the user wants to write a PR description.
resolve-conflicts
Rebase the current branch onto the target branch to resolve PR conflicts.
standup
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.
sync
Sync the current branch with the latest changes from the default branch.
tag-release-npm
Bump the npm package version, tag the release, and push.
tag-release
Suggest and apply the next semver tag based on commits since the last tag.
jira-ticket-git
Turn the current git changes into a well-formed Jira/Linear-style ticket with acceptance criteria.
Turn the following notes into a professional email. Use when the user has rough notes they want turned into a polished email.
tldr
Summarize the following text for a non-technical manager. Use when the user pastes technical content they want simplified.
review
Review code and provide structured feedback. Use when the user wants to review their changes, a file, or pasted code.
standup-git
Generate a standup update from yesterday's git commits. No input needed.
action-items
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.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.