setup-code-maintenance-bot

Topics in the source

• Set Up a Code Maintenance Bot
• 1. Establish the destination and agent
• 2. Resolve the maintenance contract
• 3. Prepare the configuration
• 4. Provision, verify, and activate
• 5. Hand off

Turn the user's maintenance intent into a runnable Paperclip routine with a named agent, accessible repository and skill, bounded work, and inspectable PRs. The maintenance skill supplies the domain judgment: test auditing, documentation upkeep, dependency maintenance, refactoring, or another chosen task. If asked only to draft instructions or a setup plan, produce that artifact and stop before provisioning or running anything. Do not perform the maintenance while setting up the bot. An immediate trial is a separate choice from scheduling. Start with the instance and agent choices, using answers already supplied: Instance: show a clickable, verified Paperclip web URL and ask which instance to use. If none is known, ask for its URL; never assume localhost, the instance used in an earlier task, or the first connected tool. Company: resolve the company within that instance; ask if ambiguous. Agent: list accessible, suitable agents with names and links, and offer use an existing agent or create a new agent. Do not silently choose. Example, after resolving the actual URL: “Use Paperclip, company Acme? Which agent should own this: an existing agent or a new one?” For a new agent, resolve

This is an excerpt. Refer to the complete source and its current requirements.