Tag

#Github

241 results found

Church Website Editor
@Elijah Desent

The Custom Website Editor lets a pastor manage and update their church's professionally-built website using plain English — no code, no logins, no technical knowledge required. It connects directly to the live website's GitHub repository, so any change you describe is made for you and ships to the real, public site within about 30 seconds. Editing your site. Ask for any wording change — fix a typo, reword a welcome message, update a service time, swap a heading, add a paragraph or a whole new section — and it finds the right page, makes the exact edit, and publishes it. It can read any page before changing it, search your site's content for a phrase you remember ("Sunday morning," "What to Expect," a pastor's name), browse your pages and files, and even create brand-new pages. Every change is saved with a clear, human-readable note so you always know what was done. Photos and videos. Send a photo and it adds it to your site; send a video or a large image and it's hosted on fast permanent storage and dropped onto the page you want. It can list the images already on your site so the right photo always shows up — no broken pictures. Undo and history. Ask "what did I change today?" and it shows your recent updates in plain language. Say "undo that" or "go back" and it safely rolls the live site back to how it was — nothing is ever lost. Knowing it worked. After any change it can confirm the site rebuilt successfully, and if something ever breaks the build, it explains what went wrong in plain English and fixes it — you never see raw errors. Your own domain. Bought a domain like yourchurch.org? It connects that domain to your site and gives you the exact, simple settings to enter at your domain registrar, including a warning if the change could affect email on that domain. Hosting, chat, analytics, and more. It can start your monthly hosting subscription, set up a live website chat widget so visitors can message you, and report how your site is doing — total traffic, your most-viewed pages, where visitors are coming from, and day-by-day trends. It can also score any church website against the Church Website Score rubric to show where it stands.

5 days ago
Instagit - Let Your Agents Instantly Understand Any Github Repo
@Instagit

Works with Claude Code, Claude Desktop, Cursor, OpenClaw, and any MCP-compatible client. The @latest tag ensures you always get the most recent version. Why Agents that integrate with external libraries are flying blind. They read docs (if they exist), guess at APIs, and hallucinate patterns that don't match the actual code. The result: broken integrations, wrong function signatures, outdated usage patterns, hours of debugging. When an agent can actually analyze the source code of a library or service it's integrating with, everything changes. It sees the real function signatures, the actual data flow, the patterns the maintainers intended. Integration becomes dramatically easier and less error-prone because the agent is working from ground truth, not guesses. What Agents Can Do With This - Integrate with any library correctly the first time — "How do I set up authentication with this SDK?" gets answered from the actual code, not outdated docs or training data. Your agent sees the real constructors, the real config options, the real error types. - Migrate between versions without the guesswork — Point your agent at both the old and new version of a library. It can diff the actual implementations and generate a migration plan that accounts for every breaking change. - Debug issues across repository boundaries — When a bug spans your code and a dependency, your agent can read both codebases and trace the issue to its root cause — even into libraries you've never opened. - Generate integration code that actually works — Instead of producing plausible-looking code that fails at runtime, your agent writes integration code based on the real API surface: actual method names, actual parameter types, actual return values. - Evaluate libraries before committing — "Should we use library A or B?" Your agent can analyze both implementations, compare their approaches to error handling, test coverage, and architectural quality, and give you a grounded recommendation. - Onboard to unfamiliar codebases in minutes — Point your agent at any repo and ask how things work. It answers from the code itself, with file paths and line numbers, not from memory that may be months out of date.

5 months ago
Gitingest-MCP
@opengig

Python
a year ago
Github
@github

a year ago